[chirp_users] Chirp and virus alarm
Just for the record:
I just tried to download latest daily build.
Avast blocked connection claiming it is malicious, infected with Win32:Evo-gen.
Tried to download both install exe and ZIP file, both were blocked.
I disabled Avast, then downloaded and installed Chirp latest daily build, but when I enable Avast it does not allow Chirp to run, still claiming it is infected by Win32:Evo-gen.
However, the latest stable build http://chirp.danplanet.com/download/0.4.1/chirp-0.4.1-installer.exe was not recognized as malicious and is not blocked. It downloaded and installed with no problem.
I guess this is false alarm but quite annoying.
Pedja YT9TP
--- This email has been checked for viruses by Avast antivirus software. http://www.avast.com
Please, everyone who has encountered this report it to Avast as a false positive.
Tom KD7LXL On Dec 12, 2014 4:48 AM, "Pedja YT9TP" yt9tp@uzice.net wrote:
Just for the record:
I just tried to download latest daily build.
Avast blocked connection claiming it is malicious, infected with Win32:Evo-gen.
Tried to download both install exe and ZIP file, both were blocked.
I disabled Avast, then downloaded and installed Chirp latest daily build, but when I enable Avast it does not allow Chirp to run, still claiming it is infected by Win32:Evo-gen.
However, the latest stable build http://chirp.danplanet.com/download/0.4.1/chirp-0.4.1-installer.exe was not recognized as malicious and is not blocked. It downloaded and installed with no problem.
I guess this is false alarm but quite annoying.
Pedja YT9TP
This email has been checked for viruses by Avast antivirus software. http://www.avast.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users
Please, everyone who has encountered this report it to Avast as a false positive.
I had that problem with the previous daily build -- it was mildly exasperating until I realized what was happening (Avast! was quietly deleting the EXE).
My workaround then was simply to whitelist the CHIRP installation directory -- and I submitted a false positive report at the time. Newer versions may need newer reports -- I’m unsure of the granularity of Avast! versioning.
However, whitelisting the directory is a one-time, everlasting workaround.
(That does of course presume that the user trusts CHIRP to remain virus-free.)
On Dec 12, 2014 9:00 AM, tom.wz9u@gmail.com wrote:
(That does of course presume that the user trusts CHIRP to remain
virus-free.)
Being open source, Chirp is pretty easy to audit.
This is not the first time Avast has incorrectly categorized popular software as a virus. It's an automated system. My guess is they don't have the resources to appropriately deal with issues like this as quickly as bigger companies like Symantec.
Tom KD7LXL
Probably worth mentioning:
At a minimum yo ushould verify the link that you are clicking to download comes from the correct site, the chirp web site.
When you are hovering over the link for the actual download it should come from chirp.danplanet.com, or trac.chirp.danplanet.com.
There are lots of malicious sites and banner ads that will try to get you to download other software or your intended software with an infected installer.
Additionally, you can verify that the checksum of the file you downloaded matches the one published on the CHIRP web site in the same folder in a file named SHA1SUMS. You need the utility sha1sum, or an equivalent that can compute a SHA-1 checksum.
http://chirp.danplanet.com/download/0.4.1/SHA1SUMS http://trac.chirp.danplanet.com/chirp_daily/LATEST/SHA1SUM
Hope this helps, --Rob
participants (4)
-
Pedja YT9TP -
Robert Terzi -
Tom Hayward -
tom.wz9u＠gmail.com