On Wed 2017-02-22 08:12:31 -0500, Peter Lebbing wrote:
> I just found out that the following two commands are equivalent:
>
>> $ gpg2 -o full.gpg --export-secret-keys ac46efe6de500b3e
>> $ gpg2 -o minimal.gpg --export-options export-minimal --export-secret-keys
>> ac46efe6de500b3e
I just confirme
On February 21, 2017 9:34:17 AM EST, "Gerd v. Egidy"
wrote:
>Hi,
>
>I'd like to announce a program I wrote to backup GnuPG and SSH keys as
>qrcodes on paper:
>
>paperbackup.py
>https://github.com/intra2net/paperbackup
>
Just wanted to say thanks for sharing your work. As for paperkey, I have a
On 22/02/17 16:10, Thomas Jarosch wrote:
> May be the internal packet format changed or needs adaption.
It is not an internal packet format by the way, it is defined in RFC
4880 (OpenPGP Message Format). And all GnuPG versions output their keys
formatted according to OpenPGP, so the problem you're
On 22/02/17 16:10, Thomas Jarosch wrote:
> When I think about long term storage, I'd rather rely on the full data
> instead of a snippet of the openpgp packets.
I understand that. However, let me point out that any errors parsing
will only occur while *creating* a backup with paperkey. Once it
suc
You were correct, Peter. I haven't had a chance to verify on Ubuntu yet, but
on Windows the following steps did the trick:
- there was no 'trusted-certs' directory in my existing home directory
(C:\users\dave\appdata\Roaming\gnupg\), so I created one. I also went ahead
and created a 'logs' di
Hi Peter,
On Wednesday, 22 February 2017 13:56:22 CET Peter Lebbing wrote:
> Oh, as an aside, the advantage of paperkey is that it is
> self-describing.
I've tried paperkey with Gnupg 2.1.13 and it had trouble parsing the secret
key data. May be the internal packet format changed or needs adapt
> Oh, as an aside, the advantage of paperkey is that it is
> self-describing.
I'll chime in with another recommendation for Paperkey. I'm a little
surprised that your code is as large as it is, too: using an alternate
pipeline you might be able to significantly reduce code size.
(a) use Python 3
On 22/02/17 13:56, Peter Lebbing wrote:
> Leaving aside this bug, export-minimal will achieve your goal: it will
> only include the currently valid parts of the key without any
> certifications by other keys.
Whoops! I made a mistake here.
export-minimal does not remove "parts of the key that are
I just found out that the following two commands are equivalent:
> $ gpg2 -o full.gpg --export-secret-keys ac46efe6de500b3e
> $ gpg2 -o minimal.gpg --export-options export-minimal --export-secret-keys
> ac46efe6de500b3e
> $ ll
> total 104
> -rw--- 1 peter peter 50731 Feb 22 14:00 full.gpg
> -
Hello Gerd!
Thank you for sharing your program with the world! I'm sure it will be
useful.
On 22/02/17 09:38, Gerd v. Egidy wrote:
> You are right that this is probably more than strictly neccessary. But if you
> look at my example output on github, a regular public and private key in
> qrcodes
Hi Daniel,
> > gpg2 --armor --export "User Name" >key.asc
> > gpg2 --armor --export-secret-key "User Name" >>key.asc
> > paperbackup.py key.asc
>
> this is a cool idea. however, it seems like you might be backing up
> more than most people would need. For most folks, their OpenPGP
> certificate
11 matches
Mail list logo
