From 67a947daddadffcef9fab89aebee9d5ba5816f79 Mon Sep 17 00:00:00 2001 From: Safihre Date: Thu, 4 Jan 2024 14:00:16 +0100 Subject: [PATCH] Update virus scanner FAQ --- wiki/faq.html | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/wiki/faq.html b/wiki/faq.html index acfed4d8..dc78e01f 100644 --- a/wiki/faq.html +++ b/wiki/faq.html @@ -325,13 +325,17 @@

Some of the files after unpacking have very strange names (

Virus scanners and false positives with new SABnzbd releases

-

In the first one or two weeks after a new SABnzbd release, a virus scanner (like Windows Defender) might say the new SABnzbd release - contains a virus / is malicious. This is caused by the new SABnzbd binary, which is new and thus unknown to some virus scanners. - After one or two weeks, the virus scanners are OK with the new release. - You can follow statistics what virus scanners say on www.virustotal.com +

+ In the first one or two weeks after a new SABnzbd release, a virus scanner (like Windows Defender) might say the new SABnzbd release + contains a virus / is malicious. + The reason for this is that SABnzbd is written in the programming langauge Python, but many malicious programs are also written in Python. + Just because of that virus scanners are triggered automatically after a new release, as the SABnzbd binary is unknown to them.
+ These results are false-positives.
+ You can upload the SABnzbd binary yourself to www.virustotal.com, which checks the binary + against all available virus scanners. If the binary did contain some virus, all the scanners would be triggered.
+ After one or two weeks, most virus scanners are updated and will no longer react to SABnzbd.

-
Footnotes