Closed GoogleCodeExporter closed 8 years ago
Message from Nod32
C:\Users\Owner\AppData\Local\Temp\CTi66CcP.7z.part could not be saved, because
the source file could not be read.
Original comment by laddspcw...@gmail.com
on 27 Feb 2012 at 10:37
-- Why would Nod32 label this as a virus?
-- Ask the developer of Nod32. We, the grub4dos team, cannot imagine why
grub4dos could be a virus. grub4dos is Free and Open-Source Software. Normally
we build the binary on Linux.
But maybe(possibly), just because of this(i.e., the fact that it is FOSS), it
is labelled as a virus. Compare to that, Linux is even considered as cancer by
MS.
Original comment by tinyb...@gmail.com
on 27 Feb 2012 at 11:03
-- Ask the developer of Nod32
Not blaming you guys at all. I have been downloading all the new releases and
this is the first Nod32 warning. It was more of out loud thinking question. I
just wanted to make sure a file wasn't corrupt on upload. I turn my nod off and
downloaded the file and all is well. Thanks for you guys and your work.
Original comment by laddspcw...@gmail.com
on 27 Feb 2012 at 11:09
Urr.... the samilar reports occurred several times. not by you, but by some
others. The reports are too many than it should be. Any way, thank you for your
report.
Original comment by tinyb...@gmail.com
on 27 Feb 2012 at 11:26
No problem. Thank you all for g4d.
Original comment by laddspcw...@gmail.com
on 27 Feb 2012 at 11:34
I had the same problem with version 0.4.6a. The day before yesterday I sent a
report by http://kb.eset.com/esetkb/index?page=content&id=SOLN141 and today no
false alarms.
Original comment by nami...@poczta.onet.pl
on 29 Feb 2012 at 11:49
I also sent a report few days ago also and I can download 0.4.6a today with no
warning from Nod. Nod is great (sometimes) :)
Original comment by laddspcw...@gmail.com
on 29 Feb 2012 at 1:08
No misdetection in later virus signature update of NOD32. Issue closed.
https://www.virustotal.com/file/91928f369152f705b90ddfbd117c1e52673398d28bf6d727
515a1b6761f1a6b9/analysis/1330605910/
Original comment by roy...@gmail.com
on 1 Mar 2012 at 12:47
Original issue reported on code.google.com by
laddspcw...@gmail.com
on 27 Feb 2012 at 10:34