From: Michael Wild <themiwi@gmail.com>
To: cygwin@cygwin.com
Subject: Re: UPX compressed setup-x86_64.exe crashes on Win10
Date: Mon, 21 Jan 2019 18:25:00 -0000 [thread overview]
Message-ID: <CAALQ5rkWjLJTkJbGrPtz3dB1k_B1HSTPLfBDOR62Y2tG8PjQVw@mail.gmail.com> (raw)
In-Reply-To: <87y37eudwo.fsf@Rainer.invalid>
On Mon, 21 Jan 2019, 18:19 Achim Gratz wrote:
> 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.
>
Thanks. I have very little hope of getting it whitelisted... Is UPX
compression really a necessity? Otherwise I'll have to resort to my custom
compiled versions.
Michael
>
--
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 18:25 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
2019-01-21 18:25 ` Michael Wild [this message]
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=CAALQ5rkWjLJTkJbGrPtz3dB1k_B1HSTPLfBDOR62Y2tG8PjQVw@mail.gmail.com \
--to=themiwi@gmail.com \
--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).