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

Define certificate creation facilities #51169

Open
danfuzz opened this issue Dec 15, 2023 · 2 comments
Open

Define certificate creation facilities #51169

danfuzz opened this issue Dec 15, 2023 · 2 comments
Labels
crypto Issues and PRs related to the crypto subsystem. feature request Issues that request new features to be added to Node.js. never-stale Mark issue so that it is never considered stale

Comments

@danfuzz
Copy link

danfuzz commented Dec 15, 2023

What is the problem this feature will solve?

Right now, there is a gap in the crypto package in that, while one can parse existing certificates (e.g., new X509Certificate(...)), there's no exposed built-in functionality (that I could find) to create new certificates with specified properties.

This feature will close that gap.

What is the feature you are proposing to solve the problem?

Add new classes and/or methods to node:crypto, so that one can create a signed certificate from its various parts, along with a signing key, CSR, etc.

What alternatives have you considered?

I am currently using the npm package pem for this, which is a thin wrapper around call-outs to the openssl binary (which it assumes is available in the environment).

The npm packagenode-forge seems to have the right functionality and is JS-native, though it is unclear how well-maintained it is.

@danfuzz danfuzz added the feature request Issues that request new features to be added to Node.js. label Dec 15, 2023
@marco-ippolito marco-ippolito added the crypto Issues and PRs related to the crypto subsystem. label Dec 16, 2023
@mcollina
Copy link
Member

mcollina commented Jan 8, 2024

I think this would be a great addition to Node.js to simplify the adoption of https even on developer machines.

Copy link
Contributor

github-actions bot commented Jul 7, 2024

There has been no activity on this feature request for 5 months. To help maintain relevant open issues, please add the never-stale Mark issue so that it is never considered stale label or close this issue if it should be closed. If not, the issue will be automatically closed 6 months after the last non-automated comment.
For more information on how the project manages feature requests, please consult the feature request management document.

@github-actions github-actions bot added the stale label Jul 7, 2024
@mcollina mcollina added never-stale Mark issue so that it is never considered stale and removed stale labels Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
crypto Issues and PRs related to the crypto subsystem. feature request Issues that request new features to be added to Node.js. never-stale Mark issue so that it is never considered stale
3 participants