New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NSOCK ERROR openssl legacy provider failed to load #2532
Comments
This is not a true error in the sense that Nmap cannot work. However, having the legacy OpenSSL provider installed will allow the use of legacy crypto that may be needed to fully probe some outdated services and devices. In our Windows builds, the legacy provider is built-in, so the load fails because it is unnecessary. I've added some checks to ensure we only print this warning when the -d option is used (debugging). |
I have also experienced this error when running Zenmap GUI 7.93. This is the output of nmap --version on the command line:
I am receiving this error whenever I run an Intense scan in Zenmap. I don't use -d for debugging, and I still see this error. The scan still runs, but this error always occurs when I run Intense scan. I've tried removing -v to disable verbose output, but I still see the error. |
I saw this error today using a copy of zenmap for windows installed today. The command I ran was; nmap -sU -p 47800-47810 --script bacnet-info 192.168.0.4 |
Solution for macOS.
For homebrew nmap
For dmg nmap
|
Describe the bug
When running a scan using NMAP Gui v7.93 on Windows 11, I get the following error:
Reading on various forums, the solution appears to be remove v7.93 and install v7.92. Was surprised I couldn't find this bug with v7.93 reported here. (Apologies if this bug is already listed, but I just failed to find it).
To Reproduce
Run v7.93 from the GUI and select Scan from the interface.
Expected behavior
Would expect it to run the scan without errors
Version info (please complete the following information):
The text was updated successfully, but these errors were encountered: