Switch branches/tags
Nothing to show
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
..
Failed to load latest commit information.
schemes
src
tests
README.md
computeAvg.py
runAStest.sh
runAutoStrong.py

README.md

AutoStrong

Many signature schemes are presented under the existential unforgeability definition wherein an adversary cannot produce a signature on a "new" message. However, strong unforgeability guarantees more - that the adversary cannot produce a "new" signature even on a previously signed message. Strongly-unforgeable signatures are often used as a building block in signcryption and chosen-ciphertext secure encryption.

There are several general transformations to obtain strongly unforgeable signatures from unforgeable signatures. We focus on the highly-efficient transformation due to Boneh, Shen and Waters (BSW) [1] that only applies if a signature is paritioned and a less efficient transformation due to Bellare-Shoup [2]. AutoStrong first automatically determines whether a given signature satisfies the partitioning property using Z3 and Mathematica. If so, it applies BSW, otherwise, it applies the BS transform to obtain a strongly unforgeable signature.

ACM CCS 2013 publication

Installation

AutoStrong requires the following external tools: Mathematica 9 and Z3 Theorem Prover.

AutoStrong generates executable code in Charm. Therefore, you must first install the Charm-Crypto framework (v0.43) to execute the automatically generated strongly unforgeable signature scheme in Python and/or C++.

Z3 Install

(Python 3 bindings available in unstable branch)

  • Clone repository: git clone https://git01.codeplex.com/z3

  • Install instructions:

    python scripts/mk_make.py --prefix=/home/leo

    cd build; make; make install

Running The Tool

For the help menu, execute the following:

python runAutoStrong.py --help
AutoStrong:  convert an unforgeable signature to a strongly unforgeable signature in SDL.

Arguments:

	-s, --sdl  [ filename ]
		: input SDL file description of scheme.

	-c, --config [ SDL config file ]
		: configuration parameters needed for AutoStrong.

	-v, --verbose   [ no-argument ]
		: enable verbose mode.

	-o, --outfile  [ filename prefix ]
		: generate code of new scheme in C++/Python for Charm.

	-b, --benchmark  [ no-arguments ]
		: benchmark AutoStrong execution time.

	-t, --skip-transform [ no-arguments ]
		: skip the application of the BSW or BS transform

	--path [ path/to/dir/ ]
		: destination for AutoStrong output files. Default: current dir.

An example for how to execute AutoStrong on the Boneh-Boyen (short) signature scheme with basic options:

python runAutoStrong.py --sdl schemes/bbssig04.sdl --config schemes/configBBSig.py -o TestBB -v

Configuration

AutoStrong requires configuration parameters to understand basic aspects of the signature scheme. The configuration file is specified in Python with the following options:

schemeType: for describing the type of input scheme. For signature types, "PKSIG".

messageVar: denotes the message being signed/verified

keygenPubVar: denotes the user's public-key

keygenSecVar: denotes the user's secret-key

signatureVar: denotes the signature if scheme type is PKSIG

masterPubVars: denotes the public parameters available to all users of the system (if applicable)

masterSecVars: denotes the master secret-key (if applicable)

We require function names of algorithms described in the SDL specified as setupFuncName, keygenFuncName, signFuncName and verifyFuncName.

See the configuration for the CL signature example below:

schemeType = "PKSIG"

setupFuncName 	= "setup"
keygenFuncName 	= "keygen"
signFuncName 	= "sign"
verifyFuncName 	= "verify"

masterPubVars = None
masterSecVars = None

keygenPubVar = "pk"
keygenSecVar = "sk" 
messageVar = "M"
signatureVar = "sig" 

References

[1]. Dan Boneh, Emily Shen, and Brent Waters. Strongly unforgeable signatures based on computational Diffie-Hellman. In PKC, pages 229 - 240, 2006.

[2]. Mihir Bellare and Sarah Shoup. Two-tier signatures, strongly unforgeable signatures, and fiat-shamir without random oracles. In PKC, pages 201 - 216, 2007.