unhandled signature subpacket type 33, added by default by GnuPG >= 2.1.14

[keisisqrl]

From keybase/keybase-issues#2668:

Signature subpacket type 33 is defined by GnuPG as issuer fingerprint (this is not (yet?) registered with IANA). Starting in 2.1.14, it was inserted by default when signing a key. The keybase client (correctly) errors out when encountering this signature type. This effectively makes keybase impossible to use in conjunction with GnuPG >= 2.1.14 or keys signed by GnuPG >= 2.1.14.

Again going by GnuPG, this subpacket (if present) should always have a length of 21. Not sure if keybase has any use for the content of this subpacket, but it should at least tolerate its presence.

[garthk]

137 days later: any way we can surface this to someone who can work on it? One of the drivers for my use of keybase is the support from vault, which in turn needs keybase pgp to work. Forcing an old version of gnupg is becoming problematic.

[maxtaco]

I think we fixed this problem, can you retry it?

[andrewhowdencom]

@maxtaco I was previously getting this issue when following someone; that seems resolved. Unsure whether it was GnuPG upgrades or whether you guys fixed it.

gpg (GnuPG) 2.1.18
libgcrypt 1.7.6-beta