projectdiscovery / projectdiscovery/tlsx
Support for SSLv2.0 and its cipher suites
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 156
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 4
Description
Are there plans for the ability to scan for SSLv2.0 and its cipher suites.
I tried using the openSSL binary from drwetter (https://github.com/drwetter/openssl-1.0.2.bad), which does allow SSLv2.0 and its cipher suites to be enumerated at TestSSL (https://github.com/drwetter/testssl.sh).
However, I had no success. If I pass the binary along as the next command, I get an empty response:
tlsx -openssl-binary openssl-1.0.2.bad/bin/openssl -sm openssl -ve -ce -u example.com
It would be great if TLSX also supported this, because I still unfortunately see occasional server support for SSLv2.0, and I don't want to miss this when using TLSX as a research tool.
Contributor guide
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 with the tlsx command shown in the issue and the -openssl-binary and -sm openssl options. Check how TLS versions and cipher suites are enumerated, then verify that an SSLv2-capable OpenSSL binary reports SSLv2.0 and its cipher suites for the example command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100