uNetworking / uNetworking/uWebSockets
Throw exception or stop the listener when SSL used but compiled without WITH_OPENSSL=1
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 19k
- Forks
- 1.9k
- Avg merge
- 3h 24m
- Merged PRs (30d)
- 5
Description
There also seems to be no warnings/errors if uWS is compiled without "WITH_OPENSSL=1" . It compiles and executes without using an ssl context even when the code tells it to.
Originally posted by @yuumikazoomi in https://github.com/uNetworking/uWebSockets/issues/1132#issuecomment-800413035
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
Start by locating the SSL listener setup and the build path controlled by WITH_OPENSSL=1. Reproduce the case where SSL is requested without OpenSSL support, then add coverage showing that the listener reports the configuration problem by throwing or stopping. The issue is over four years old with no recent discussion or linked pull request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100