I'm only using a few tools from the Win64 package:
nlcrc.exe
nldiff.exe
nlupd.exe
But my Windows 10 x64 doesn't allow me to use them because of a
detected trojan: https://www.microsoft.com/en-us/wdsi/threats/malware-encyclopedia-desc ription?name=Trojan%3AWin32%2FWacatac.B!ml&threatid=2147735505
When I have it analysed at virustotal:
https://www.virustotal.com/gui/file/92f3fee1ed8822fd4e3239cf391bd14e2e e0d3be0440d23ff7e18a76f8288ab2/detection
Only Microsoft detects it as such out of 72 scanners. But still this
is inconvenient...
DOS-DPMI, OS/2-libc066, Win32-msvc6dll, Win64-msvc10dll uploaded to:
http://download.huskyproject.org https://sites.google.com/view/vasilyevmax/
Only Microsoft detects it as such out of 72 scanners. But still this
is inconvenient...
I had a similar case with a commercial program. Microsoft antivirus was the
only one on virustotal marking the program as a threat. I wrote to the program support and the next day Microsoft antivirus was excluded from the set of the antimalware testing the program. :) And the support advised to include their program in Microsoft antivirus exclusions on my computer.
Only Microsoft detects it as such out of 72 scanners. But still
this is inconvenient...
I had a similar case with a commercial program. Microsoft
antivirus was the only one on virustotal marking the program as a
threat. I wrote to the program support and the next day Microsoft
antivirus was excluded from the set of the antimalware testing
the program. :) And the support advised to include their program
in Microsoft antivirus exclusions on my computer.
Still this is inconvenient, because everybody that is going to want to
use the windows compiled husky binaries, is going to encounter this problem.
I don't know if this would be easy, and if it helps, but maybe it's possible to use another compiler (like mingw), to create the windows binaries for the husky set of tools?
Still this is inconvenient, because everybody that is going to want to
use the windows compiled husky binaries, is going to encounter this problem.
I don't know if this would be easy, and if it helps, but maybe it's
possible to use another compiler (like mingw), to create the windows
binaries for the husky set of tools?
Still this is inconvenient, because everybody that is going to want to
use the windows compiled husky binaries, is going to encounter this
problem.
Not everybody.. :)
I don't know if this would be easy, and if it helps, but maybe it's
possible to use another compiler (like mingw), to create the windows
binaries for the husky set of tools?
Compiled here with Openwatcom..
https://www.virustotal.com/gui/file/d45522c0eccaf9d51f2d30efe9e113317efd05a
4d57c57b58cb150234377605c
| Sysop: | Nitro |
|---|---|
| Location: | Portland, OR |
| Users: | 3 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 253:50:34 |
| Calls: | 136 |
| Files: | 751 |
| Messages: | 89,316 |