Open leedavis81 opened 10 years ago
Yes, the private key should be identical. I would restart with your key backups and reimport them into keybase using the keybase push --update
command. It will ask you if you want to add username@keybase.io
to your key, simply say no (because this will change the value of the initial key) and the feature that it supports isn't live just yet.
My recollection is that the key encryption is randomized. On Mar 27, 2014 8:47 AM, "Lee Davis" notifications@github.com wrote:
When creating a key from the keybase interface you get an option to download the private key and / or upload it to keybase for convenience.
In the event of you saving the private and allow keybase to store it; performing an "Export my private key from Keybase" provides you a similar but different private key. In my experience after a few hundred characters the key begins to change.
I'm no crypto export, but I'd assume these keys should identical.
Further to this, performing a gpg --import of the originally downloaded key (offered on creation) results in:
gpg: no valid OpenPGP data found. gpg: Total number processed: 0
However attempting an import of the exported key (offered after keybase storage) succeeds.
Reply to this email directly or view it on GitHubhttps://github.com/keybase/keybase-issues/issues/390 .
When creating a key from the keybase interface you get an option to download the private key and / or upload it to keybase for convenience.
In the event of you saving the private and allow keybase to store it; performing an "Export my private key from Keybase" provides you a similar but different private key. In my experience after a few hundred characters the key begins to change.
I'm no crypto export, but I'd assume these keys should identical.
Further to this, performing a gpg --import of the originally downloaded key (offered on creation) results in:
gpg: no valid OpenPGP data found. gpg: Total number processed: 0
However attempting an import of the exported key (offered after keybase storage) succeeds.