Git/testssl.sh
1
0
Fork 0
mirror of https://github.com/drwetter/testssl.sh.git synced 2026-10-04 23:48:13 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3162 from testssl/instructions

Browse Source 
better instructions
This commit is contained in:
Dirk Wetter
2026-09-29 16:52:04 +02:00
committed by GitHub
parent eeef7a72c0 815999d760
commit 0bb6581629
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
SECURITY.md
+6
View File
@@ -12,6 +12,12 @@ Disclosure](https://en.wikipedia.org/wiki/Full_disclosure_(computer_security)#Co
to have a PoC, it will be much appreciated but it is not mandatory. Using [Full Disclosure](https://en.wikipedia.org/wiki/Full_disclosure_(computer_security)#Full_disclosure) might be a problem for the people setting up a website using testssl.sh as a scanner or users. to have a PoC, it will be much appreciated but it is not mandatory. Using [Full Disclosure](https://en.wikipedia.org/wiki/Full_disclosure_(computer_security)#Full_disclosure) might be a problem for the people setting up a website using testssl.sh as a scanner or users.
Also keep in mind that the maintainers here have a professional attitude but this project, it is a spare time project. Also keep in mind that the maintainers here have a professional attitude but this project, it is a spare time project.
### How do I do that?
"Create new Issue" --> "Report a security vulnerability" . Then on the LHS you should see "Advisory" which you need to fill out. That stays private until we fixed your point or disregard it.
The UI is not very intuitive, thus if that doesn't work file a public issue that **this doesn't work**.
## Supported Versions ## Supported Versions