Thank you Grischa,
$ md5sum released/tcc-0.9.24-win32-bin.zip
bfea695874e79e5c3cf7f66ead3760e2 *released/tcc-0.9.24-win32-bin.zip
This matches. So I got the right files. Thank you.
Maybe the worm was compiled with TinyCC?
Surely not, since the alerts already happen with some of the example
Rüdiger Plantiko wrote:
Dear tcc authors and users,
the binaries generated by tcc are classified as Worm (Zhelatin) or even
Trojan by my AV programs Kaspersky resp. Norton AV. This is very likely a
wrong classification but makes it hard to work with tcc for me.
Just to go sure: Is there an
Dear tcc authors and users,
the binaries generated by tcc are classified as Worm (Zhelatin) or even
Trojan by my AV programs Kaspersky resp. Norton AV. This is very likely a
wrong classification but makes it hard to work with tcc for me.
Just to go sure: Is there an official MD5 checksum for the