* Samuel Henrique:
> Looking at nmap changelog, it seems like this issue has been going
> back and forth[0] and had stabilized after some point (I guess that's
> when most AV vendors added the signature), this means that any changes
> in the compilation might trigger the issue again.
>
> Hilko,
I just realized I accidentally triggered this issue because I enabled
some hardening flags for this executable on the last upload (in
testing and sid right now):
https://salsa.debian.org/pkg-security-team/nmap/-/commit/e8002cd93757bb8e579821da032beac10245dd05
This change caused the binary to end
Hi Kim-Alexander. On behalf of the Nmap Project, I just wanted to say
thanks for submitting the false positive file to all the AV vendors. That
really helps.
-Fyodor
Good evening,
I've submitted the file in question to numerous AV vendors (Sophos,
Avast, Microsoft, McAfee, BitDefender, PandaSecurity, ...) and so far
all I've heard back from have removed offending signatures from their
databases or at the very least whitelisted the file. The latter of
Hello,
Granted, this is a false positive and could be fixed through other channels if
I absolutely had to have nmap installed, but...
This a corporate antivirus which I have no ability to personally override.
Arguing with company IT about it is more trouble than just uninstalling an only
* Dom Sekotill:
> /usr/share/nmap/nselib/data/psexec/nmap_service.exe is detected by
> Sophos AV as malware.
The antivirus installation is apparently misconfigured. In the local
filesystem context, the program is not even directly runnable. In the
context of .deb transfer by APT this should not
Package: nmap-common
Severity: normal
Dear Maintainer,
/usr/share/nmap/nselib/data/psexec/nmap_service.exe is detected by Sophos AV as
malware. This appears to be a common problem with psexec, both with nmap's
implementation and Microsoft's:
https://seclists.org/nmap-dev/2010/q1/198
7 matches
Mail list logo
