From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [Bug] Re3gression in setup handling of SHA512 checksum failures
Date: Wed, 21 Mar 2018 19:30:00 -0000 [thread overview]
Message-ID: <e59f4ab2-2ae9-6076-2c6a-8bf682b8706c@cornell.edu> (raw)
In-Reply-To: <874llaik21.fsf@Rainer.invalid>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
On 3/20/2018 4:11 PM, Achim Gratz wrote:
> Ken Brown writes:
>> I'll look into both of these issues, unless Jon beats me to it.
>
> Thanks.
>
>> By the way, this only affects local installs. For network installs,
>> the hash gets checked at an earlier stage.
>
> That's correct. I forgot to mention that, but all my installs are from
> a local mirror (necessary due to the way network access is restricted at
> my workplace)
I haven't been able to come up with a safe way to recover from a
checksum error at this point, at least not without a lot of work. I
propose that we just bail out with an appropriate error message in this
situation.
Patch attached.
Ken
[-- Attachment #2: 0001-Give-a-fatal-error-on-a-checksum-failure-during-inst.patch --]
[-- Type: text/plain, Size: 1238 bytes --]
From 0607cb5da1bbe61cd132499082a62bbbc54c8dfd Mon Sep 17 00:00:00 2001
From: Ken Brown <kbrown@cornell.edu>
Date: Wed, 21 Mar 2018 14:03:00 -0400
Subject: [PATCH setup] Give a fatal error on a checksum failure during install
This only affects local installs, where the hash of an archive is not
checked until we reach do_install_thread(). At this point it seems
too late to recover safely.
---
install.cc | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/install.cc b/install.cc
index 37dea6f..b5adcc6 100644
--- a/install.cc
+++ b/install.cc
@@ -850,7 +850,15 @@ do_install_thread (HINSTANCE h, HWND owner)
}
catch (Exception *e)
{
- yesno (owner, IDS_SKIP_PACKAGE, e->what());
+ // We used to give the user a yes/no option to skip this
+ // package (with "no" meaning install it even though the
+ // archive is corrupt), but both options could damage the
+ // user's system. In the absence of a safe way to recover, we
+ // just bail out.
+ if (e->errNo() == APPERR_CORRUPT_PACKAGE)
+ fatal (owner, IDS_CORRUPT_PACKAGE, version.Name().c_str());
+ // Unexpected exception.
+ throw e;
}
{
md5sum_total_bytes_sofar += version.source()->size;
--
2.16.2
next prev parent reply other threads:[~2018-03-21 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 18:23 Achim Gratz
2018-03-20 20:01 ` Ken Brown
2018-03-20 20:11 ` Achim Gratz
2018-03-21 19:30 ` Ken Brown [this message]
2018-03-22 0:35 ` Brian Inglis
2018-03-22 14:42 ` Ken Brown
2018-03-23 2:37 ` Brian Inglis
2018-03-22 22:01 ` Jon Turney
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=e59f4ab2-2ae9-6076-2c6a-8bf682b8706c@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@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).