Closed ulrichard closed 10 years ago
I never tried to use keyParser.py. But it work well with gpg keytocard command. Here is a pretty good tutorial that worked for me. Watch out that your keys looks like this:
sub 1024R/41320871 created: 2013-06-08 expires: 2014-06-08 usage: S
sub 1024R/B47AED2F created: 2013-06-08 expires: 2014-06-08 usage: E
sub 1024R/4495E34E created: 2013-06-08 expires: 2014-06-08 usage: A
And that your key is at most a 2048 RSA.
Am I right that I have to use a patched, self compiled version of gpg? Every stock version of gpg or gpg2 that I tried so far, refused to move the keys to the yubikey, while it was never a problem with the CryptoStick. What exact version would I have to use to compile my custom gpg? I followed https://github.com/Yubico/ykneo-openpgp/pull/10 but there seems to be no answer on the gnupg mailing list to the suggested patch.
That was the information I needed. Ubuntu saucy ships pgp2.20. So I grabed pgp2.22 from the trusty repository.
Maybe I'm doing something wrong, but I did my best in following the advice from README.gpgkeytoneo. here is what I get:
This happens for all three sub keys. The fact that I can successfully export them suggests that the keys themselves are ok.
Maybe this information is also of value. I created the keys according to this recipe: http://ncommander.blogspot.ch/2009/08/so-after-having-my-trusty-sony-vaio-do.html I also have them on a crypto stick. But for the neo, I got the .gnupg directory like it was before the initial transfer to the other card. So all the private keys are still in the gpg files.