uNetworking / uNetworking/uWebSockets.js
Allow for dynamically-generated certificates, keys, etc.
Open
Nobody has claimed this yet.
enhancement
low priority
- Dominant language
- C++
- Stars
- 9.2k
- Forks
- 625
- Avg merge
- 6h 7m
- Merged PRs (30d)
- 13
Description
Packages like node-forge let us dynamically generate self-signed certificates, private/public key pairs, etc. Developer experience can be significantly improved if we didn't have to save them to file and just pass them in directly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name specific files, tests, or entry points. Start by reviewing the existing certificate and key loading API and how Node.js values are passed into the native layer. Done means dynamically generated certificates and key pairs can be supplied directly without first being written to files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, nodejs
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100