So then it looks like dmtxwrite is the issue then?
;)
John
From: john espiro
To: David Shaw
Sent: Sat, March 20, 2010 11:56:30 PM
Subject: Re: Paperkey (Was: Re: )
Hi David -
If I do:
paperkey --secret-key
./secring.gpg --output raw.paperkey
On Mar 13, 2010, at 5:22 AM, john espiro wrote:
> Hi there -
>
> Thanks to your help, and David's, I have tried a few other things. Using
> yoru script I found that indeed it was dtmx that was failing due to the file
> being larger than 1555 bytes.
>
> I deleted all of the commented lines suc
Hi there -
Thanks to your help, and David's, I have tried a few other things. Using yoru
script I found that indeed it was dtmx that was failing due to the file being
larger than 1555 bytes.
I deleted all of the commented lines such as this, and then ran dtmxwrite:
# Secret portions of key C8
I've used the `dtmx` tool to export some GPG keys (exactly a 4096
bits one) and it worked.
What I did was something like:
paperkey --secret-key ./key.gpg --output ./key.paperkey
--output-type raw
dmtxwrite --encoding 8 --format png --resolution 72
<./key.paperkey >./key.png
Hi David -
Thanks for the quick reply.
I should note that I am on a Windows XP box.
When I run gpg --export-secret-key m...@key.com | paperkey --output-type raw
for both the 2048 and 4096, I note that the output for the 4096 key is about
10% logner than that of the 2048 key.
I am not familia
On Mar 11, 2010, at 3:16 AM, john espiro wrote:
> I am using paperkey 1.2 from http://www.jabberwocky.com/software/paperkey/
> and
> dmtxwrite version 0.7.3
> libdmtx version 0.7.3
>
> If I run this command:
> gpg --export-secret-key my...@me.com | paperkey --ignore-crc-error
> --output-type r
Sorry for the empty subject... fixed now
From: john espiro
To: gnupg-users@gnupg.org
Sent: Thu, March 11, 2010 7:25:45 AM
Subject:
I am using paperkey 1.2 from http://www.jabberwocky.com/software/paperkey/
and
dmtxwrite version 0.7.3
libdmtx version 0.7.3