unhandled signature subpacket type 33, added by default by GnuPG >= 2.1.14
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
From https://github.com/keybase/keybase-issues/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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the OpenPGP signature subpacket parser and its handling of unknown types. Use signatures generated by GnuPG >= 2.1.14 to verify that subpacket type 33, with its expected length of 21, is tolerated without errors; no repository file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100