public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin@cygwin.com
Subject: Re: Unable to Verify 64 bit Installer on Windows
Date: Thu, 30 Dec 2021 21:51:33 +0000	[thread overview]
Message-ID: <DB3PR0202MB356106D57B41BA8026702CB1E7459@DB3PR0202MB3561.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <CAPwDAhA1mFg9=QkU6OU_1BFC_Sz500yJ2+YpQgzf1p-i2Lyabw@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 889 bytes --]

On 30/12/2021 21:24, Greg Williamson wrote:
> Hello,
>
> While attempting to verify the installer found here:
> https://cygwin.com/install.html
>
> GPG verification for "setup-x86_64.exe" failed with "BAD signature from
> "Cygwin <cygwin@cygwin.com>". I also created a SHA512 hash of the 
> installer
> and it did not match the one posted here:
> https://cygwin.com/sha512.sum
>
> As a sanity check I attempted to verify the 32bit version "setup-x86.exe".
> The SHA512 matched and the GPG signature verification succeeded.
>
> I thought I'd report here in case there was a security issue. Thank you in
> advance for your assistance!
>
> ~Greg
>
This is concerning. I recently re-installed Cygwin so I'm glad I marked 
my packages as test. I hope those weren't compromised installers, though 
hopefully my antivirus would have stopped anything nefarious.

Hamish


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3175 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2021-12-30 21:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 21:24 Greg Williamson
2021-12-30 21:51 ` Hamish McIntyre-Bhatty [this message]
2021-12-30 22:58 ` Brian Inglis
2021-12-30 23:38 ` 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=DB3PR0202MB356106D57B41BA8026702CB1E7459@DB3PR0202MB3561.eurprd02.prod.outlook.com \
    --to=hamishmb@live.co.uk \
    --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).