From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: UPX compressed setup-x86_64.exe crashes on Win10
Date: Mon, 21 Jan 2019 17:19:00 -0000 [thread overview]
Message-ID: <87y37eudwo.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAALQ5rnmuEtm6208hQd2qo9FKWmdT=N7RFEg5QqqaZeCgoG3vQ@mail.gmail.com> (Michael Wild's message of "Mon, 21 Jan 2019 09:03:32 +0100")
Michael Wild writes:
> Anybody else experiencing this? I tried trawling through the mailing
> list, but nothing specific turned up. Maybe this is an interaction
> with the BLODA imposed on me by our company IT policy. But then I'd
> expect others to have seen this issue too.
It wouldn't be the first time antivirus heuristics target UPX routines
instead of actual malware code. You'll have to wait for the vendor or
your organization to whitelist the relatively new setup.exe (unless
you're allowed to do that yourself).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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:[~2019-01-21 17:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 8:03 Michael Wild
2019-01-21 17:19 ` Achim Gratz [this message]
2019-01-21 18:25 ` Michael Wild
2019-01-21 19:55 ` Achim Gratz
2019-01-21 21:12 ` Michael Wild
2019-01-22 16:53 ` Brian Inglis
2019-01-22 17:28 ` Michael Wild
2019-01-22 18:34 ` Achim Gratz
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=87y37eudwo.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).