public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygwin x11 doesn't start after windows 10 upgrade
Date: Tue, 16 Jun 2020 06:59:51 +0200	[thread overview]
Message-ID: <87ftavvc54.fsf@Otto.invalid> (raw)
In-Reply-To: <A206248F-2270-4767-8616-3A2BADFDC00D@vodafone.de> (Vodafone Holger's message of "Mon, 15 Jun 2020 00:21:24 +0200")

Holger, Vodafone writes:
> At least I know, that TrendMicro is on my System, if someone can help
> me, which folder is meant to be added to the TrendMicro Exceptions I
> can check with our internal IT.

If the root-kit-like character of some of their components and the many
CVE in TrendMicro that essentially do the opposite of what the product
is promised to do hasn't already convinced your administrators to get
rid of it, you should exempt the Cygwin installation directory from all
their heuristics and "on-line" check and mitigation facilities.  How
exactly to do this varies, but in a corporate environment these are
usually not modifiable by the user.


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

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  parent reply	other threads:[~2020-06-16  4:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 15:57 Steinar Bang
2020-06-13  6:30 ` Marco Atzeri
2020-06-13  9:30   ` Steinar Bang
2020-06-13 11:22     ` Marco Atzeri
2020-06-13 12:00       ` Steinar Bang
2020-06-13 13:22         ` Marco Atzeri
2020-06-13 15:48           ` Steinar Bang
2020-06-13 16:44             ` Steinar Bang
2020-06-13 20:37       ` Andrey Repin
2020-06-13  9:35   ` Steinar Bang
2020-06-13  9:55     ` Steinar Bang
2020-06-13 11:31       ` Marco Atzeri
2020-06-13 12:03         ` Steinar Bang
2020-06-13 12:09           ` Steinar Bang
2020-06-13 13:14         ` Holger, Vodafone
2020-06-13 13:29           ` Marco Atzeri
2020-06-13  9:04 ` Steinar Bang
2020-06-13 21:15   ` Jon Turney
2020-06-14 10:44     ` Steinar Bang
2020-06-14 11:18       ` Henry S. Thompson
2020-06-14 16:12         ` Steinar Bang
2020-06-14 17:49           ` Marco Atzeri
2020-06-14 21:45             ` Steinar Bang
2020-06-14 22:21               ` Holger, Vodafone
2020-06-15 12:17                 ` Holger, Vodafone
2020-06-15 12:57                   ` Holger, Vodafone
2020-06-16  4:22                   ` Brian Inglis
2020-08-02 20:25                   ` Steinar Bang
2020-08-02 21:00                     ` Eliot Moss
2020-08-04 12:01                       ` Steinar Bang
2020-08-04 13:12                         ` Hamish McIntyre-Bhatty
2020-08-04 16:55                         ` ASSI
2020-06-16  4:59                 ` ASSI [this message]
2020-07-02 15:01               ` Steinar Bang
2020-07-02 22:12                 ` Holger, Vodafone
2020-06-16 11:46     ` Holger, Vodafone
2020-06-26  9:15       ` Holger, Vodafone
2020-07-02 14:42         ` Steinar Bang
2020-06-14  6:18 ` Marco Atzeri
2020-06-14 10:38   ` Steinar Bang

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=87ftavvc54.fsf@Otto.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).