Re: How to export ASCII armored secret key without passphrase?

On 01/20/2016 07:13 PM, Peter Lebbing wrote: > Is your GnuPG 2.1.10 binary invoked as "gpg", not as "gpg2"? Which OS is this > and where did you get GnuPG 2.1.10? This might be an issue if you want to > install GnuPG 1.4 alongside. I believe in Debian, the plan is to name the 2.1 > binary gpg and t

Re: How to export ASCII armored secret key without passphrase?

On Wed, Jan 20, 2016 at 6:13 PM, Peter Lebbing wrote: > $ gpg2 --export-secret-keys | gpg --import Thanks! On my system, Arch, that’s: $ gpg --export-secret-keys | gpg1 --import ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg

Re: How to export ASCII armored secret key without passphrase?

On 20/01/16 17:48, Felix E. Klee wrote: > Is there any workaround? Install GnuPG 1.4 alongside your 2.1.10 (they co-exist perfectly, but they store keys separately). It then should be something like this: $ gpg2 --export-secret-keys | gpg --import Give some temporary passphrase, passes key from

How to export ASCII armored secret key without passphrase?

There’s a known issue: Is there any workaround? For example, could I export an ASCII armored key with a passphrase, then decrypt the exported key? Command that failed without passphrase (the key doesn't have one): $ gpg --armor --export-secret-keys >k