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

Clarify the usage of encodings which can result in non-determinism #166

Open
highlunder opened this issue Apr 11, 2024 · 3 comments
Open
Assignees

Comments

@highlunder
Copy link
Collaborator

Examples include general byte encodings of extensions, or the handling of otherName in General Name (Types)

@highlunder
Copy link
Collaborator Author

This is related to the bigger determinism-issue discussed in #197

@gselander
Copy link
Collaborator

Check if the same strategy as in #197 applies to otherName

@gselander gselander self-assigned this Dec 19, 2024
@gselander
Copy link
Collaborator

otherName in general is encoded [ ~oid, bytes ]. The three negative values in the Section 9.9 C509 General Names Registry register encodings for otherName with BundleEID / SmtpUTF8Mailbox / hardwareModuleName.

This opens for different encodings, so for deterministic encoding it is required to introduce some restrictions, for example only use the dedicated encodings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants