Stephan Beck [2016-11-24 16:51:00Z] wrote: > A1) Install the monkeysphere package (1) that includes openpgp2ssh tool > A2) Export the secret subkey you'd like to use for ssh authentication > purposes and pipe it through openpgp2ssh > gpg2 --export-secret-subkeys \ > --export-options export-reset-subkey-passwd [keyID!] | \ > openpgp2ssh [keyID] > gpg-auth-keyfile
Not too pretty but it works. Thank you. Since it creates a separate key which is not tied to my secring.gpg the case left me wondering what will happen when I upgrade to gpg 2.1 in the future. I mean I'll run gpg 2.1 someday and it will convert my secring.gpg to some KEYGRIP.key files, including my A-capable key. Will the authentication key be the same and technically compatible with the key that I just created with openpgp2ssh and ssh-add commands? Just wondering. It's not that important. Some manual work is probably necessary anyway at the first upgrade. -- /// Teemu Likonen - .-.. <https://github.com/tlikonen> // // PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///
signature.asc
Description: PGP signature
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
