public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: "Buchbinder, Barry (NIH/NIAID) [E]" <barry.buchbinder@nih.gov>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: setup (2.917)
Date: Wed, 26 Jan 2022 08:47:25 +0000	[thread overview]
Message-ID: <20220126084725.tguohvzaiq2duepc@lucy.dinwoodie.org> (raw)
In-Reply-To: <SA9PR09MB5389E23454C6AD643EC982459B5F9@SA9PR09MB5389.namprd09.prod.outlook.com>

On Tue, Jan 25, 2022 at 10:33:52PM +0000, Buchbinder, Barry (NIH/NIAID) [E] via Cygwin wrote:
> On Mon, Jan 24, 2022 at 6:12 PM Bill Stewart wrote:
> >
> >On Mon, Jan 24, 2022 at 3:49 PM Buchbinder, Barry (NIH/NIAID) [E] via Cygwin wrote:
> >
> >Windows protected your PC
> >> Microsoft Defender SmartScreen prevented an unrecognized app from starting.
> >> Running this app might put your PC at risk.
> >>
> >
> >Not to state the obvious, but this means that the Microsoft antivirus program prevented it from running.
> >
> >Exclude it.
> 
> I have no control over the antivirus, so cannot exclude it.
> 
> The point was that this wasn't a problem with 2.915, so most likely is the result of some change made in 2.917.
> 
> However, this morning, after a reboot, it seems to work OK.

The difference was entirely that the new setup installer was new.
Microsoft Defender SmartScreen learns what programs are safe by seeing
how many people download and use them, on the basis that things that are
downloaded by lots of people and don't become known as a specific threat
should be fine, whereas something unknown may well be some new malware.

This flag doesn't indicate there's anything about 2.917 that had changed
to worry about, only that it had changed and that you were one of the
first to try to use it.

If you don't have the ability to override the spurious warning, your
only options will be to wait longer before using the new version, so
SmartScreen has a chance to learn it's safe from people who can click
past the warning, or to take it up with whoever manages your systems.
There is nothing the Cygwin project folks could do to help other than
never release new software.

There's a bit more information on the "reputation" checking under "How
Microsoft Defender SmartScreen works when a user tries to run an app" at
https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-smartscreen/microsoft-defender-smartscreen-set-individual-device

(For the sake of explicitness, I am a Microsoft employee these days, but
SmartScreen is nothing to do with my role at Microsoft, and Cygwin is at
best tangential.  I don't have any more knowledge or influence in this
area than any non-employee.)

Adam

  reply	other threads:[~2022-01-26  8:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 22:33 Buchbinder, Barry (NIH/NIAID) [E]
2022-01-26  8:47 ` Adam Dinwoodie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-24 22:49 Buchbinder, Barry (NIH/NIAID) [E]
2022-01-24 23:12 ` Bill Stewart
2022-01-24 20:02 Jon Turney
2022-01-27  7:28 ` Shaddy Baddah
2022-01-28 14:56   ` Jon Turney
2022-01-31  3:06     ` Shaddy Baddah
2022-01-31  5:36 ` © Fxzx mic
2022-01-31  6:25   ` Marco Atzeri
2022-01-31  6:43     ` © Fxzx mic
2022-01-31  8:20       ` Samuel Lelièvre
2022-01-31 12:13       ` Jon Turney
2022-01-31 15:46         ` Andrey Repin
2022-01-31 19:56           ` Brian Inglis

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=20220126084725.tguohvzaiq2duepc@lucy.dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=barry.buchbinder@nih.gov \
    --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).