From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Symantec AntiVirus False Positive
Date: Wed, 25 Oct 2017 03:42:00 -0000 [thread overview]
Message-ID: <d149123a-0a9c-1b30-bcb8-ad7f480cc4d3@SystematicSw.ab.ca> (raw)
In-Reply-To: <87fua8vzmj.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me>
On 2017-10-24 18:29, J.McNamara wrote:
>
> Harrod, Norm (UJS) writes:
>
>> https://www.symantec.com/security_response/writeup.jsp?docid=2010-051308-1854-99&vid=4294919973
>>
>> setup-x86_64.exe
>> RISK WS.Reputation.1
See https://sourceware.org/ml/cygwin/2017-07/msg00097.html after last setup change.
>> Unfortunately, this will not allow for use on business networks using
>> Symantec. Not sure who controls the approval of Reputation for Cygwin.
Symantec - they just rate everything they have not excluded (e.g. real risks to
you from big commercial products, and them from big vendor lawyers, such as MS
Office, Adobe suites, Oracle Java) as a "Reputation" risk, which generates a lot
of false positives they expect the smaller vendor developers to resolve with
them, and leaves a lot of open source projects without the resources to do that,
and their users, stuck. Symantec's Dispute page now gives 404!
There should be a setting or option on warning, to allow you to bypass these
"reputation risks", as they are unsupported by any evidence. You org may have a
group policy in effect to disallow this, and you may have to follow up
internally to have this bypassed for https://cygwin.com/setup-x86{_64}.exe: they
can validate the HTTPS cert and the gpg/pgp
https://cygwin.com/setup-x86{_64}.exe.sig if they want to be sure.
Remember Symantec outsourced all this to India starting in 2004, and recently
had to divest their CAs and businesses to a competent CA, after a number of
certification problems were not responded to or addressed to the satisfaction of
the CA/Browser Forum (of which Symantec are a founding member), and criticisms
of Symantec neither following nor auditing CA practices, led by Google Chrome
and Mozilla root CA teams.
> I used to have problems with rebase getting stuck. I tried to bring it
> to Webroots attention. They had this laundry list of all this stuff to
> do to submit a ticket. I told them it is a problem. It is not enough to
> do that. They wanted to me to be a tester. I thought I am convincing
> enough so no thanks.
The OP can see if there are any usable links in the Symantec product Quarantine
section to report a false positive, and look in their Tools/NoSupport directory
for utilities to take programs out of quarantine, mentioned on their web site.
Better AV products allow this with a click, with another to report it as a false
positive and submit a sample. Many AV products report a false positive on any
(sometimes every) upgrade of installers and system level utilities, until
someone complains.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-10-25 3:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aa6dfc973cbe41e19845a3191cdf3c99@SD3EXC06A.k12.sd.local>
[not found] ` <daf2c312e4b3495ab9f9767fd89d2ade@SD3EXC06A.k12.sd.local>
2017-10-24 18:11 ` Symantec Virus Harrod, Norm (UJS)
2017-10-25 0:29 ` J.McNamara
2017-10-25 3:42 ` Brian Inglis [this message]
2017-10-25 9:35 ` Andrey Repin
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=d149123a-0a9c-1b30-bcb8-ad7f480cc4d3@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).