Unknown signature subpacket: 34 (error 905)

[jb3]

When trying to add a key of type ED25519 I'm getting the error shown below:

❯ keybase pgp select --multi
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?    DFCB1EA39C66CEE8             Joe Banks <[email protected]>
2    4096R   F9E39305CE213394             Joseph Banks <[email protected]>
Choose a key: 1
▶ ERROR key generation error: Unknown signature subpacket: 34 (error 905)

Client details

GPG version: 2.2.29 Keybase version (client + service): 5.8.1

[skull-squadron]

This is still a problem. I can't use keybase because of this.

$ gpg --list-secret-keys --keyid-format=long
~/.gnupg/pubring.kbx
-------------------------------
sec   ed25519/5ACF93DDB1D667C4 2022-02-08 [SC] [expires: 2025-02-07]
      96F74575F7C5E84CD3776CAB5ACF93DDB1D667C4
uid                 [ultimate] Barry Allard <[email protected]>
ssb   cv25519/2DA398BA00FF5C75 2022-02-08 [E] [expires: 2025-02-07]
ssb   rsa4096/844C9B77D0F3A4C0 2022-02-08 [S] [expires: 2025-02-07]
ssb   rsa4096/C52DD48846102732 2022-02-08 [E] [expires: 2025-02-07]
ssb   rsa4096/DDAEC925E6537AC3 2022-02-08 [A]

[skull-squadron]

Update: I'm surprised they're still shipping at all, albeit incompatible with GPG. It's great for web developers and weekend hobbyists but it's a let-down for anything real. Plus, it's a centralized SPoF dependent on a corporation and not privacy friendly. Best to seek key sharing alternatives for the time being.

• Keybase 6.0.1 for macOS (CLI and desktop)
• gpg (GnuPG) 2.3.6

Also doesn't work when migrating keys to a Yubikey, which also doesn't change anything:

sec>  ed25519/5ACF93DDB1D667C4 2022-02-08 [SC] [expires: 2025-02-07]
      96F74575F7C5E84CD3776CAB5ACF93DDB1D667C4
      Card serial no. = xxxx xxxxxxxx
uid                 [ultimate] Barry Allard <[email protected]>
ssb#  cv25519/2DA398BA00FF5C75 2022-02-08 [E] [expires: 2025-02-07]
ssb   rsa4096/844C9B77D0F3A4C0 2022-02-08 [S] [expires: 2025-02-07]
ssb   rsa4096/C52DD48846102732 2022-02-08 [E] [expires: 2025-02-07]
ssb   rsa4096/DDAEC925E6537AC3 2022-02-08 [A]
ssb>  rsa2048/F97FA3B4028B8FD7 2022-06-04 [E] [expires: 2027-06-03]

[tuupola]

I experience the same problem.

$ gpg --list-secret-keys --keyid-format=long
~/.gnupg/pubring.kbx
--------------------------------
sec   ed25519/F0391E9782AE4ABE 2022-05-06 [SC]
      3F6EE8F2EE36C580D90BA762F0391E9782AE4ABE
uid                 [ultimate] Mika Tuupola <[email protected]>
ssb   cv25519/7B7535483250243D 2022-05-06 [E]
ssb   ed25519/B90E23D8BDDD1754 2022-05-06 [S]

$ keybase pgp select                        

...

#    Algo   Key Id             Created   UserId
=    ====   ======             =======   ======
1    255?   F0391E9782AE4ABE             Mika Tuupola <[email protected]>
Choose a key: 1
▶ ERROR key generation error: Unknown signature subpacket: 34 (error 905)

$

[ikkerens]

Same problem here, perhaps it's related to the fact that all of us are using ECC keys?

[szxxx]

I have an RSA key and have the same error message

[dollannn]

Still not working

[rafa-dot-el]

Same issue here, I can't import my key, for tests purposes it works with normal GPG, Github and other tools (github.com/rafa-dot-el.gpg)

-----BEGIN PGP PUBLIC KEY BLOCK-----

mDMEY4D8jRYJKwYBBAHaRw8BAQdAjyFTGmJWK+vM0ZM/m+pqJdo36R6Po/U59wKY
XOcerkC0RFJhZmFlbCAoR2l0aHViIEdQRykgPDEwNDY4ODMwNStyYWZhLWRvdC1l
bEB1c2Vycy5ub3JlcGx5LmdpdGh1Yi5jb20+iJMEExYKADsWIQRfCz6s8fmBVQlG
zfVGnjJVpA0q1gUCY4D8jQIbAwULCQgHAgIiAgYVCgkICwIEFgIDAQIeBwIXgAAK
CRBGnjJVpA0q1sQ4AQDHxuEPmPLb5Pb9Hiyjvu0vbF+a49k3rJnwbxIH4IwPOAEA
n2NIkNw9s3pS8wlyfRdm/pdLOIoLOLZs4iai6uhFqQq4OARjgPyNEgorBgEEAZdV
AQUBAQdArEDqdrCYeQaX0+cdcdjrpIVYPn8WZGAf/MhEdM+31icDAQgHiHgEGBYK
ACAWIQRfCz6s8fmBVQlGzfVGnjJVpA0q1gUCY4D8jQIbDAAKCRBGnjJVpA0q1gb1
AP0QQnllgwwQxYlDXLgU2qzxI+OvFJOwLpuyn8SyMe44fgD/VL36jd+FNsY/6h4i
uR5jqdROHYtUrVK3rjUEO7gzgwY=
=tA7a
-----END PGP PUBLIC KEY BLOCK-----

[erAck]

Seems to be a duplicate of https://github.com/keybase/keybase-issues/issues/4025

[aellwein]

same here

[gill6151]

Seems to be a duplicate of #4025

There would not need to be duplicates if they actually fixed the problem