Open 706f6c6c7578 opened 7 years ago
Hello, thank you for using Keybase! Unfortunately, this curve is not supported by our crypto stack. It's not very popular outside of crypto-currencies, also it's not a curve type that's supported by go-crypto, so some new code is needed to support it. Until there is more interest, pull request are welcome: https://github.com/keybase/go-crypto and https://github.com/keybase/kbpgp
Thanks for your reply. I hope it can be implemted soon. Since keybase allows users to publish their Bitcoin address too, i had the following idea: User could create in a safe environment a private BTC key and it's address derived from a secret GnuPG secp256k1 sub signing key. This would allow users to bind a BTC address to a public GnuPG sub key, which can be verified by users. :-)
P.S. noteworthy also that one can generate an OpenPGP key pair from a Bitcoin key... https://github.com/Jaxx-io/openpgpjs-secp256k1/blob/master/README_secp256k1.md
Last but not least, here people can read and verify that i did a Bitcoin Transaction to a member of the GnuPG team, with my converted secp256k1 secret key. https://lists.gnupg.org/pipermail/gnupg-users/2017-September/059002.html
Hi dear keybase team,
i just created two sub keys, secp256k1, for signing and encryption and when uploading my pub key to keybase via the web interface i get the following error:
Error: Unknown curve OID: 2b8104000a
Best regards Stefan