-
luke-jr commented at 8:54 PM on January 18, 2016: member
- laanwj added the label Windows on Jan 19, 2016
-
laanwj commented at 9:44 AM on January 19, 2016: member
That's weird. Can anyone verify that the windows signature is correct?
-
jonasschnelli commented at 9:48 AM on January 19, 2016: contributor
Just checked, 32/64 signatures are correct.
-
PRabahy commented at 12:42 PM on January 19, 2016: contributor
bitcoin-0.12.0rc1-win64-setup.exe looks clean except for McAfee-GW-Edition.
-
MarcoFalke commented at 1:12 PM on January 19, 2016: member
@PRabahy You'd have to install it to reproduce the issue, I guess.
-
paveljanik commented at 1:21 PM on January 19, 2016: contributor
@MarcoFalke virustotal (see the link) does that for you.
The same applies to win32. BehavesLike.Win32.Suspicious.rc detected.
-
MarcoFalke commented at 3:38 PM on January 19, 2016: member
@paveljanik Do you have sources to support your claim? (Keep in mind installing is different from executing the installer)
-
MarcoFalke commented at 3:47 PM on January 19, 2016: member
Can't reproduce the reported bug "Avast had suspicion on the exe and made him run on a sandbox."
-
c-nagy commented at 7:45 PM on January 20, 2016: none
Could it be the Avast Firewall? Have you tried disabling only that?
-
laanwj commented at 4:28 PM on January 25, 2016: member
I don't think we had any further reports of this issue. May have been a local misconfiguration, or maybe AVAST keeps statistics on how many times a certain executable has been run with their scanner installed and balks if it's only seen it very few times.
Neither do I see any solution at our side to this. Something to consider in the future may be to code-sign the bitcoin-qt.exe executable as we do the installer, but this would be hard to integrate into the gitian process. And I'm not sure it would solve this.
- laanwj closed this on Jan 25, 2016
- MarcoFalke locked this on Sep 8, 2021
