From: Dan Harkless <cygwin-list21@harkless.org>
To: cygwin@cygwin.com
Subject: Re: Cygwin setup reporter as malware
Date: Wed, 7 Dec 2022 13:54:04 -0800 [thread overview]
Message-ID: <14e7843a-5829-2c74-313b-13d08b37243e@harkless.org> (raw)
In-Reply-To: <AS8PR07MB714100AE9CFC6D5AAEE34179D91A9@AS8PR07MB7141.eurprd07.prod.outlook.com>
On 12/7/2022 8:20 AM, Sylwester Rutkowski via Cygwin wrote:Hi,
> The setup-x86_64.exe is reported as malicious at https://www.virustotal.com/gui/file/edd0a64dc65087ffe453ca94b267169b39458a983b29ac31320fcaa983d0f97e/detection
>
> Can this be resolved somehow?
No. It's normal and common for software like Cygwin, which has the
power to be used maliciously (as opposed to, say, a Minesweeper game or
something), to have false positives on VirusTotal for a handful of
vendors. I've never heard of SecureAge or Trapmine (hmm, maybe it
*would* flag Minesweeper...), and I'm pretty well educated in the
anti-malware space, so if it were me, I'd just ignore those false
positives and pay attention to the credible AV software results (and the
Community Score).
If you have some corporate policy requiring things to have 0 detections
on VirusTotal or something, your only recourse is to contact the
SecureAge and Trapmine vendors and convince them somehow to fix their
false positives.
--
Dan Harkless
http://harkless.org/dan/
next prev parent reply other threads:[~2022-12-07 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 16:20 Sylwester Rutkowski
2022-12-07 21:54 ` Dan Harkless [this message]
2022-12-09 11:39 ` Oskar Skog
2022-12-09 17:51 ` Dan Harkless
2022-12-09 18:49 ` Christian Franke
2022-12-08 0:46 ` Bill Stewart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14e7843a-5829-2c74-313b-13d08b37243e@harkless.org \
--to=cygwin-list21@harkless.org \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).