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

Document the x509 and asn1 packages #946

Open
pav-kv opened this issue Jun 10, 2022 · 0 comments
Open

Document the x509 and asn1 packages #946

pav-kv opened this issue Jun 10, 2022 · 0 comments

Comments

@pav-kv
Copy link
Contributor

pav-kv commented Jun 10, 2022

The x509 and asn1 are forks of the corresponding standard Go packages.

Their README files need more detail on:

  • The reasons why the packages are forked.
  • How to maintain them.
  • How/when to keep up with the upstream changes.

The latter are important since there is a backlog of x509-related issues:


"Why" in a nutshell: Since there are many implementations of x509 in the ecosystem, with various levels of incompleteness, CT logs need to be permissive of certificates that almost follow the spec.

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

No branches or pull requests

1 participant