Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Botan doesn't support large OIDs #4020

Open
jdoubleu opened this issue Apr 14, 2024 · 1 comment
Open

Botan doesn't support large OIDs #4020

jdoubleu opened this issue Apr 14, 2024 · 1 comment
Labels
enhancement Enhancement or new feature

Comments

@jdoubleu
Copy link

Botan cannot store OIDs with large subidentifiers. The standard (ITU-T X.660, ITU-T X.680) does not limit the number range on any subidentifier other than the root arc and some secondary identifiers.

For example, 2.299.62133450347103072435436460230495464564354 is a valid OID, but cannot be stored by Botan. That is, because Botan stores the subidentifiers as uint32_t.

While the above example may be unrealistic, there's a valid use-case for 128bit numbers: Arc 2.25. allows for UUIDs to be embedded inside its OID (see ITU-T X.667 and http://oid-info.com/get/2.25).

See also: https://misc.daniel-marschall.de/asn.1/oid_facts.html#chap4

@randombit
Copy link
Owner

TBH I had not heard of this 2.25 arc before for UUIDs. I'd be pretty inclined to go with "that's interesting but I doubt anyone uses it", especially as RFC 5280 only requires implementations support OID elements up to 2^28, but I see for example Go has recently introduced a new OID type to handle such UUIDs in certificate policies. :/

@randombit randombit added the enhancement Enhancement or new feature label Apr 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhancement or new feature
Projects
None yet
Development

No branches or pull requests

2 participants