search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

Document migration from SHA1 for existing keys #4094

Open raxod502 opened 2 years ago

raxod502 commented 2 years ago

I encounter the error

▶ ERROR key generation error: no valid primary key self-signature or key(s) have expired (Signature failure in packet 1: rejecting insecure hash SHA1 (98a50086f826a705)) (error 905)

when attempting to upload my public key to Keybase. This prevents me from using Keybase at all.

I see that there is a workaround at https://github.com/keybase/client/issues/22458#issuecomment-584179988 with the strong disclaimer

I have a limited knowledge of what might break if you do this and other people already have your public key. Also if my real keys where at stake here, I would backup my secret keys beforehand.

As such, I do not feel comfortable following the procedure. Could you (the Keybase maintainers) please publish an officially endorsed and verified-safe procedure for working around this error?

cezmunsta commented 8 months ago

Just to say that it is ironic that this is nearly 2 years old and on RHEL I cannot install keybase because of SHA1 being used (#4207)