public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Cowan <brian.cowan@hcl.com>
To: Jon Turney <jon.turney@dronecode.org.uk>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: RE: Does the Cygwin setup program do internal sanity checks on startup?
Date: Wed, 31 Aug 2022 12:14:35 +0000	[thread overview]
Message-ID: <SI2PR04MB5821E6F82723979640AD175AFE789@SI2PR04MB5821.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <9c93aa09-880b-be4c-1532-68f492e2aabd@dronecode.org.uk>

Well, is it possible to use 7zip? It seems like you can do something like it in: https://superuser.com/questions/42788/is-it-possible-to-execute-a-file-after-extraction-from-a-7-zip-self-extracting-a

Not that I think this would help with heuristics, and some AV tools REALLY don't like executing things from users' temp directories. (Which .Net applications seem to like to do sometimes.)

Maybe have compressed and uncompressed installers?

Brian Cowan
HCL Software
Technical Specialist, ClearCase SWAT
brian.cowan@hcl.com


-----Original Message-----
From: Cygwin <cygwin-bounces+brian.cowan=hcl.com@cygwin.com> On Behalf Of Jon Turney
Sent: Sunday, August 28, 2022 11:46 AM
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Does the Cygwin setup program do internal sanity checks on startup?

[CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don't click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.]

On 25/08/2022 19:14, Brian Cowan via Cygwin wrote:
> And this was exactly it. I downloaded the latest UPX version, and it
> crashed on startup. I downloaded the Linux version on another host,
> copied the setup program to that host and extracted it there. NOW I
> can update Cygwin...

I wonder if UPX compression of setup makes as much sense now as it did
20+ years ago.

Not only does it (occasionally) generate problems like this, but also with malware detection heuristics.

OTOH, not using it would make setup ~4x larger.
::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________

  reply	other threads:[~2022-08-31 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 20:46 Brian Cowan
2022-08-25 16:52 ` Adam Dinwoodie
2022-08-25 17:11   ` Jon Turney
2022-08-25 18:14     ` Brian Cowan
2022-08-28 15:46       ` Jon Turney
2022-08-31 12:14         ` Brian Cowan [this message]
2022-09-03 13:02           ` Andrey Repin

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=SI2PR04MB5821E6F82723979640AD175AFE789@SI2PR04MB5821.apcprd04.prod.outlook.com \
    --to=brian.cowan@hcl.com \
    --cc=cygwin@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /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).