Kagarus
Member
- Sep 28, 2017
- 413
- 774
- 296
Yeah, Chrome (and Firefox, since in the backend they're using the same crap from google) raising false alarms because of their lists are a well-known issue here, and honestly I think they're becoming a net-negative (basically, when you habituate users to click away your security popups because of constant false positives, they'll also be more likely to ignore them when it matters - my worry is that the habit will transfer to some degree to other security measures like the phishing protection).
Easiest way to see if this is the case is to download a copy from the "dangerous" filehoster and another from presumed safe one and compare them (sha256sum, certutil -hashfile) (this doesn't help if someone passed an actual malicious file to the uploaders here, that needs to be caught by the uploaders or by yourself, for example using diffs).
And sorry for being a bit caustic earlier, was operating on way too little sleep.
