Paperkey 1.0 released

[Hideki Saito]

Hello,
Paperkey is great, and I've put up some Japanese introduction of the tool.
http://d.hatena.ne.jp/unsignedint/20090122/1232679511

One thing I saw on Windows version is that piping doesn't work. It
seems like it corrupt the output when redirection is used, so this
could be something to do with the operating system, but just reporting
the issue. (Earlier GnuPG on Windows also had same problem, for
example, gpg --export > foobar would cause corrupted data on foobar,
not sure it's related.)

So on Windows,
instead of doing,
gpg --export-secret-key 51A00A8E | paperkey --output output.txt
I have to do
gpg --output output.sec --export-secret-key 51A00A8E
paperkey --secret-key output.sec --output output.txt

Thank you.
-- 
Hideki Saito



2009/1/22 David Shaw <dshaw at jabberwocky.com>:
> On Thu, Jan 22, 2009 at 04:52:48PM -0600, Kevin Hilton wrote:
>> Thanks for this release.  Reading the explanation on the website:
>> http://www.jabberwocky.com/software/paperkey/ got me thinking.  Is
>> there an explanation or description of all the metadata that is
>> contained within the secret key?
>
> Yes.  See RFC 4880, sections 5.5.3 and 11.2.  What makes paperkey
> possible is that in OpenPGP, a secret key is actually the same thing
> as a public key with a few extra fields tacked on (the ones specified
> in 5.5.3).
>
> Another nice side effect of this is that you can transform any secret
> key into a public key.  In fact, GPG will do this for you - try
> importing a secret key that you don't already have a public key for.
> GPG will import the secret key, and then create a public key for it
> automatically.
>
> David
>
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
>