public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Sophos Antivirus
Date: Tue, 09 Apr 2019 16:38:00 -0000	[thread overview]
Message-ID: <87h8b7jfqi.fsf@Rainer.invalid> (raw)
In-Reply-To: <8675fd88-d4a9-d022-885f-f03fa2082390@cs.umass.edu> (Eliot Moss's	message of "Mon, 8 Apr 2019 18:06:22 -0400")

Eliot Moss writes:
> At present, Sophos is enterprise managed on my computer, which means
> I can't even personally install the hotfix, but I might convince my
> organization to help me do it, etc.  Just gathered information while
> I await their response ...

No experience with Sophos, but certain heuristics in virus scanners
apparently are only applied when the file in question has not yet been
scanned.  So it is sometimes helpful to run an explicit scan of the
install dir.

With other antivirus solutions only explicit whitelisting or exclusion
of the installation directory actually helped.  The exclusion usually
only needs to target the "real-time" and heuristic engines of the
antivirus package, which might make it more acceptable for corporate IT
security.  It is also helpful to ask them to escalate to the vendor
support, since usually the vendors know about how their products
interact with Cygwin and have a solution ready for when the customer
asks.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

--
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

      reply	other threads:[~2019-04-09 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 22:06 Eliot Moss
2019-04-09 16:38 ` Achim Gratz [this message]

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=87h8b7jfqi.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).