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 > -rw------- 1 peter peter 50731 Feb 22 14:00 minimal.gpg > $ gpg2 --version > gpg (GnuPG) 2.1.18 > libgcrypt 1.7.6-beta > [...]
I thought "well this is surely a bug in the new 2.1, what with the new secret key storage". But: > $ gpg -o full.gpg --export-secret-keys ac46efe6de500b3e > $ gpg -o minimal.gpg --export-options export-minimal --export-secret-keys > ac46efe6de500b3e > $ ll > total 88 > -rw-r--r-- 1 peter peter 41465 Feb 22 14:02 full.gpg > -rw-r--r-- 1 peter peter 41465 Feb 22 14:02 minimal.gpg > $ gpg --version > gpg (GnuPG) 1.4.18 > [...] And now I'm confused... surely export-minimal is useful when backing up your secret key and storage is limited? We just encountered this with the paperbackup.py thread... This works fine, BTW: > $ gpg2 -o minimal.gpg --export-options export-minimal --export > ac46efe6de500b3e$ ll > total 56 > -rw-r--r-- 1 peter peter 50631 Feb 22 14:06 full.gpg > -rw-r--r-- 1 peter peter 2623 Feb 22 14:06 minimal.gpg Cheers, Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at <http://digitalbrains.com/2012/openpgp-key-peter>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
