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
nmap does not include ndiff, impossible to compare results #23321
Comments
It doesn't look like ndiff has been updated to python2, which is now EOL. |
Debian has a huge patch to make it Py3, not sure if we want this https://salsa.debian.org/pkg-security-team/nmap/-/commit/a47969f12dd5cfbf2cb520d5b1774abd2d79044e#3a02b372872b4be170a369cfb9ebf3e76e6d9469 |
If it is not too much work to maintain I would vote for patch, so people can diff network scan results. |
Given the nebulous situation around nmap licensing, I don't think we can/should act on this at the moment. Pinging @Piraty for awareness |
giving recent license mess (#27866) i'm not even in the mood to backport this patch (nmap/nmap#1484) if it's merged. |
as nmap does not include ndiff i can't compare network scan result with previous run. ndiff seems to be python script included with nmap > 4.80, see https://salsa.debian.org/pkg-security-team/nmap/-/blob/debian/master/debian/ndiff.install
System
Expected behavior
ndiff is available
Actual behavior
i can't compare nmap results with previous run
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: