Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
SSL-ENUM-CIPHERS: Probe may give false negative aborting complete cipher detection #254
In cases where target servers have restricted ciphers and/or protocol (SSLv3), the initial 2 probes sent to detect whether the target server is running TLS/SSL may fail with "no cipher suites in common" or "Client requested protocol SSLv3 not enabled or not supported".
If we detect an SSL alert it is probably safe to assume that the target server is running TLS/SSL so continue with full scan.
Thanks for the comment, you are right! It looks like some server implementations may just kill the connection when an alert is generated, thus not sending a response. Perhaps adding an argument that forces full scan for ciphers may be an option.
My apologies for my lack of knowledge, this is my first time dealing with LUA.
NSE has a feature for forcing a script to run, bypassing the rule function.
I did notice while investigating this that we did not fix the