Posts: 1.977
Threads: 25
Joined: Sep 2009
Reputation:
31
11-24-2015, 09:28 PM
(This post was last modified: 11-24-2015, 09:32 PM by tsunami2311.)
So Avast flaged a this file as Threat:Win32:malware-gen = severity high
Seeing as this was part of PCSX2 I reported it false positive, This same false postive is flaging any Pcsx2 Git build with that file in which terminates the download fiqure i let you's know too
Posts: 3.206
Threads: 68
Joined: Mar 2010
Reputation:
110
Location: Netherlands
11-24-2015, 11:15 PM
(This post was last modified: 11-24-2015, 11:15 PM by Ryudo.)
PCSX2 1.3.1-182 for example doesn't flag padnull for me, but all recent versions of PCSX2 do flag it. It's a bit odd.
Something in the code must have changed to become flagged by AV.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 32 GB (2x16GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Samsung 980 1TB | Windows 10 Pro x64 (22H2)
Posts: 15.303
Threads: 431
Joined: Aug 2005
Reputation:
352
Location: Athens,Greece
Or they changed their detected signatures and started falsely detecting it
Posts: 3.206
Threads: 68
Joined: Mar 2010
Reputation:
110
Location: Netherlands
11-24-2015, 11:27 PM
(This post was last modified: 11-24-2015, 11:27 PM by Ryudo.)
Did padnull get any changes in the code though in the more recent versions?
If it's truly just the AV being crappy, then -every- padnull should be flagged. But it's only happening in the recent versions.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 32 GB (2x16GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Samsung 980 1TB | Windows 10 Pro x64 (22H2)
Posts: 21.718
Threads: 401
Joined: Sep 2013
Reputation:
476
Location: 私の夢の中
Yeah I originally said in BPH it happened all the way back to 1.2.1 but I was mistaken, scanned the wrong archive heh.
Does anyone know EXACTLY what revision we changed over to VS2015 in? I can't tell by the buildbot page and I'd like to verify this.
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Posts: 12.837
Threads: 48
Joined: Oct 2013
Reputation:
252
I'd say it's because of new malware. the last code change for padnull.dll was 3 months ago