letsencrypt / letsencrypt/boulder
genmtpki: use RELATIVE-OID encoding
Open
@jsha is already working on this.
Since Sep 11, 2026.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Draft 06 of merkle-tree-certs will change the encoding of issuer IDs to use a relative OID instead of the UTF8String we already use. Update genmtpki to do this.
Note that relative OIDs (class universal, tag number 36) are not currently implemented in encoding/asn1 or cryptobyte, so we'll have to do a little encoding ourselves.
Contributor guide
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.
Assessment
This issue has not been assessed yet.