Open client4 opened 7 years ago
You're right! I don't think we support cv25519
encryption keys.
Whomp whomp. Thanks for letting me know!
Ack! I just rerolled my key to use ECC and then ran into this :( -- please support cv25519
It is in progress.
On Fri, Dec 16, 2016 at 8:11 AM Juan Benet notifications@github.com wrote:
Ack! I just rerolled my key to use ECC and then ran into this :( -- please support cv25519
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/keybase/keybase-issues/issues/2506#issuecomment-267591114, or mute the thread https://github.com/notifications/unsubscribe-auth/AA05_3SvBq4434ta-6QjhffN5HZLngl0ks5rIo4WgaJpZM4Jm-gr .
Are there any news about this issue? When do you plan to support cv25519
?
We're close. We have code in that have to vendor and release. We've just been insanely busy working on features that are more popular, so it's a balancing act as you can imagine.
I would also like to see this feature. Although I picked secp256k1 as my algorithm.
@maxtaco Is this still close to being implemented?
@maxtaco Is this still close to being implemented?
I was able to add a ed25519 key as of relatively recently (October I believe). I don't think the client handles it properly (algo shows as that 256?), but it does get pushed to Keybase.
I have also been able to import my key without any errors.
The situation I am running into is trying to use keybase to encrypt an AWS IAM Access Key Secret via terraform (https://www.terraform.io/docs/providers/aws/r/iam_access_key.html). It fails with:
Error: Error encrypting IAM Access Key Secret: error parsing given PGP key: openpgp: unsupported feature: unsupported oid: 2b060104019755010501
Hopefully this is just an issue with Terraform using an old client then that is cool but I was guessing that was not the case as this issue is still open. If this is indeed fixed I'd like to know in what version it was fixed so that I can add that information to any issue that I raise in the Terraform project.
To clarify, are you getting the key from Keybase into Terraform? It's very possible the version of GnuPG running may not support ECC keys.
Woops just came back to this and realised I never answered the question.
@plttn Not sure I fully understand your question. I don't know how Terraform is doing it, I assume it is using the keybase client library.
This looks relevant for me at least https://github.com/hashicorp/terraform-provider-aws/issues/9769
I'm assuming that ed25519 is supported in keybase now.
❯ keybase pgp encrypt -m "Hello"
-----BEGIN PGP MESSAGE-----
Comment: https://keybase.io/download
Version: Keybase Go 5.5.0 (darwin)
wU4DPRx9XI4v+K4SAQdAOh8oLdvUGeLCj06wPgNsmjvUV7hDRzom+9PB7yi/0ygg
lHs7Cup1aZZtm5saAsvjkiI5el6bTgz4A+oD0KDIJ2vS4AHkEj7R8jDf59K0ZuUB
dSeoHeGZSeDo4MDhmbLgyeJHL0KM4GHi8LtvKeDc4HzgM+QVFGfOHoVWAHz8WtyW
9MeV4oJkm9DhZiIA
=M35B
-----END PGP MESSAGE-----
Any idea what version this was added in?
$ keybase pgp select
You are selecting a PGP key from your local GnuPG keychain, and
will publish a statement signed with this key to make it part of
your Keybase.io identity.
Note that GnuPG will prompt you to perform this signature.
You can also import the secret key to *local*, *encrypted* Keybase
keyring, enabling decryption and signing with the Keybase client.
To do that, use "--import" flag.
Learn more: keybase pgp help select
# Algo Key Id Created UserId
= ==== ====== ======= ======
1 255? ADFE984091983F93 name <email>
Choose a key: 1
▶ ERROR ImportKey (secret: false) error: openpgp: unsupported feature: unsupported oid: 2b06010401da470f01
It appears my PGP key doesn't work....