Issue 116 in keyczar: make "usekey" available and consistent in all keyczartool implementations

[key...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 116 by jtu...@gmail.com: make "usekey" available and consistent
in all keyczartool implementations
http://code.google.com/p/keyczar/issues/detail?id=116

The usekey command would make it much easier to produce equivalent keysets
and ciphertext across various implementations of keyczar.

I wrote three scripts to produce test data on Java, Python and C#
https://gist.github.com/4519944

Because Java and C# had use key commands, and python just didn't have it
exposed, C++ doesn't have it at all.

modified python version here
http://code.google.com/r/jtuley-keyczar-python-usekey-exposed/source/checkout

Most of the scripts are identical, in fact it was only the usekey lines,
that needed to be different.

I think an addition that would help create more integration tests would be
to have a --format flag that could take:

crypt
sign
sign-timeout
sign-unversioned
sign-attached
crypt-session
crypt-signedsession

to produce the various wire formats.

crypt-session
would likely need a destination2

and

crypt-signedsession
Would require a location2, crypter2, as well to handle the fact that two
keysets are used.

[key...@googlecode.com]

Comment #1 on issue 116 by jtu...@gmail.com: make "usekey" available and

consistent in all keyczartool implementations
http://code.google.com/p/keyczar/issues/detail?id=116

Updated python to output all wire formats in
jtuley-keyczar-python-usekey-exposed

[key...@googlecode.com]

Comment #2 on issue 116 by jtu...@gmail.com: make "usekey" available and

consistent in all keyczartool implementations
http://code.google.com/p/keyczar/issues/detail?id=116

Examples of usage for "usekey" that will produce all wire formats, if
implemented for C++/java along with issue 115, then test data production
could be produced and changed from a single borne shell script.

$KEYPROG usekey --location="${TESTDATA}/aes"
--destination="${TESTDATA}/aes/1.out" --format=crypt "This is some test
data"

$KEYPROG usekey --location="${TESTDATA}/hmac"
--destination="${TESTDATA}/hmac/2.out" --format=sign "This is some test
data"

$KEYPROG usekey --location="${TESTDATA}/hmac"
--destination="${TESTDATA}/hmac/2.timeout" --format=sign-timeout "This is
some test data" 2012-12-21T11:11:00Z

$KEYPROG usekey --location="${TESTDATA}/hmac"
--destination="${TESTDATA}/hmac/2.unversioned"
--format=sign-unversioned "This is some test data"

$KEYPROG usekey --location="${TESTDATA}/hmac"
--destination="${TESTDATA}/hmac/2.attached" --format=sign-attached "This is
some test data"

$KEYPROG usekey --location="${TESTDATA}/hmac"
--destination="${TESTDATA}/hmac/2.secret.attached"
--format=sign-attached "This is some test data" "secret"

$KEYPROG usekey --location="${TESTDATA}/rsa.public"
--destination="${TESTDATA}/rsa/2.session.material"
--destination2="${TESTDATA}/rsa/2.session.ciphertext"
--format=crypt-session "This is some test data"

$KEYPROG usekey --location="${TESTDATA}/rsa.public"
--location2="${TESTDATA}/dsa"
--destination="${TESTDATA}/rsa/2.signedsession.material"
--destination2="${TESTDATA}/rsa/2.signedsession.ciphertext"
--format=crypt-signedsession "This is some test data"

[key...@googlecode.com]

Comment #3 on issue 116 by jtu...@gmail.com: make "usekey" available and

consistent in all keyczartool implementations
http://code.google.com/p/keyczar/issues/detail?id=116

Re-patched feature in to it's own commit

http://code.google.com/r/jtuley-keyczar-python-usekey-exposed/source/detail?r=f9e408a106a307fb4a0cf87f02a34c933cf157b5

[key...@googlecode.com]

Comment #4 on issue 116 by jtu...@gmail.com: make "usekey" available and

consistent in all keyczartool implementations
http://code.google.com/p/keyczar/issues/detail?id=116

added matching 'usekey' command flags, built upon clone submitted for Issue
104

http://code.google.com/r/jtuley-java-usekey-interop/source/detail?r=81dd34095bf843a5d1a4a5ec4d49bd8107554b06

[key...@googlecode.com]

Updates:
Blockedon: keyczar:115 keyczar:128 keyczar:131

Comment #6 on issue 116 by jtu...@gmail.com: make "usekey" available and

consistent in all keyczartool implementations
http://code.google.com/p/keyczar/issues/detail?id=116

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings