Support for SSLv2.0 and its cipher suites
Maintainers usually reply within 5 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- networking, security
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.
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.
- Dominant language
- Go
- Stars
- 1.2k
- Forks
- 161
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 10
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from projectdiscovery/tlsx
-
bump Go toolchain for CVE-2026-111943Possibly taken @dogancanbakir claimed this 17 days ago. OpenType: Maintenance
projectdiscovery/tlsx#1020 · 1 assignee ·
Maintainers usually reply within 5 days
-
Update zcrypto dependency to support TLS 1.3Possibly taken @dwisiswant0 claimed this 305 days ago. Open
projectdiscovery/tlsx#879 · 2 comments · 3 reactions · 1 assignee ·
Maintainers usually reply within 5 days
-
Type: Enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
projectdiscovery/tlsx#710 · 1 comment ·
Maintainers usually reply within 5 days
-
Type: Enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
projectdiscovery/tlsx#453 · 2 comments ·
Maintainers usually reply within 5 days
All issues in projectdiscovery/tlsx
Similar issues
-
[Bug] Custom tool truncation leaves unused stream copies openPossibly taken @OUAO-FRANK claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[v3] KeyBindingManager calls (Add/Remove) are not converted into a case-insensitive accelerator.KeyOpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
crmne/hyprmoncfg#114 · 1 comment ·
Maintainers usually reply within 1 day
-
runtime: usleep sleeps nanoseconds instead of microseconds on linux/mips and linux/mips64Possibly taken @BRobertson7 claimed this today. Opencompiler/runtime
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100