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

Consider using peculiar/X509 vs PKIjs #47

Open
rmhrisk opened this issue Jan 18, 2024 · 1 comment
Open

Consider using peculiar/X509 vs PKIjs #47

rmhrisk opened this issue Jan 18, 2024 · 1 comment

Comments

@rmhrisk
Copy link

rmhrisk commented Jan 18, 2024

Is your feature request related to a problem? Please describe

No.

Describe the solution you'd like

We are the authors of PKI.js and ASN.1js and were looking at projects that took a dependency on our libraries so I started looking at consumers like njs-acme.

We noticed that you import PKI.js but implement your own x509 parser. We created a higher-level library than PKI.js called peculiar/x509.

Your code would be simpler if you consumed our x509 library instead of PKI.js, it would also allow you to have more uniform code for your x509 parsing use cases.

Describe alternatives you've considered

Suggestion

Additional context

N/A

@ivanitskiy
Copy link
Contributor

Thanks for the feedback. I agree 100% that it would simplify the code and make it consistent. as far I remember, x509 did not work in NJS env (NJS is not 100% compliant with JavaScript implementation). I will try to repro and update this issue. x509 is in use from this https://github.com/nginx/njs-examples/blob/master/njs/http/certs/js/x509.js ( it's just a copy-paste as there is no NPM artifact)

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