From: Thomas Sanders <tsanders@trellisware.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: URGENT: BAD signature from "Cygwin <cygwin@cygwin.com>"
Date: Thu, 29 Sep 2016 00:05:00 -0000 [thread overview]
Message-ID: <B0BF22335C47694D8CF77683CF7C809C8451E60E@TWHQ-MAIL1.trellisware.com> (raw)
In-Reply-To: <125363965.20160929001342@yandex.ru>
Thanks for the reply, here is the actual script. I must have copy/pasted the wrong info previously.
###
wget -q http://cygwin.com/setup-x86.exe -O ${DESTINATION}/setup-x86.exe
wget -q http://cygwin.com/setup-x86.exe.sig -O ${DESTINATION}/setup-x86.exe.sig
wget -q http://cygwin.com/setup-x86_64.exe -O ${DESTINATION}/setup-x86_64.exe
wget -q http://cygwin.com/setup-x86_64.exe.sig -O ${DESTINATION}/setup-x86_64.exe.sig
wget -q http://cygwin.com/key/pubring.asc -O ${DESTINATION}/pubring.asc
if [ $(gpg --list-keys | grep -c 'cygwin@cygwin.com') != 1 ]
then
gpg --import ${DESTINATION}/pubring.asc
fi
echo "testing ${DESTINATION}/setup-x86.exe"
gpg --verify ${DESTINATION}/setup-x86.exe.sig ${DESTINATION}/setup-x86.exe
if [ ${?} -gt 0 ]
then
mv ${DESTINATION}/setup-x86.exe ${DESTINATION}/setup-x86.exe.DONT_USE-BAD_SIGNATURE
fi
echo "testing ${DESTINATION}/setup-x86_64.exe"
gpg --verify ${DESTINATION}/setup-x86_64.exe.sig ${DESTINATION}/setup-x86_64.exe
if [ ${?} -gt 0 ]
then
mv ${DESTINATION}/setup-x86_64.exe ${DESTINATION}/setup-x86_64.exe.DONT_USE-BAD_SIGNATURE
fi ###
Here is the output:
testing /tftpboot/PXE/mirrors/cygwin//setup-x86.exe
gpg: Signature made Fri 09 Sep 2016 02:20:02 AM PDT using DSA key ID 676041BA
gpg: BAD signature from "Cygwin <cygwin@cygwin.com>"
testing /tftpboot/PXE/mirrors/cygwin//setup-x86_64.exe
gpg: Signature made Fri 09 Sep 2016 02:20:05 AM PDT using DSA key ID 676041BA
gpg: Good signature from "Cygwin <cygwin@cygwin.com>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 1169 DF9F 2273 4F74 3AA5 9232 A9A2 62FF 6760 41BA
--
Thomas Sanders | Sr. Network Systems Administrator
TrellisWare Technologies, Inc.
Office/FAX: 858-753-1654 | Mobile: 619-512-3311
-----Original Message-----
From: Andrey Repin [mailto:anrdaemon@yandex.ru]
Sent: Wednesday, September 28, 2016 2:14 PM
To: Thomas Sanders; cygwin@cygwin.com
Subject: Re: URGENT: BAD signature from "Cygwin <cygwin@cygwin.com>"
Greetings, Thomas Sanders!
> FYI, I don't know if this is working as designed (please see the
> application error below) wget https://cygwin.com/setup-x86.exe wget
> https://cygwin.com/setup-x86.exe.sig
> gpg --verify setup-x86.exe.sig setup-x86.exe
> gpg: Signature made Fri 09 Sep 2016 02:20:02 AM PDT using DSA key ID
> 676041BA
> gpg: Good signature from "Cygwin <cygwin@cygwin.com>"
-------^^^^^^^^^^^^^^
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg: There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 1169 DF9F 2273 4F74 3AA5 9232 A9A2 62FF 6760
> 41BA
> When running the app the following error occurs (Windows 7)
> This version of C:\Users\tsanders\cygwin_setup-x86.exe is not
> compatible with th e version of Windows you're running. Check your
> computer's system information to see whether you need a x86 (32-bit)
> or x64 (64-bit) version of the program, and then contact the software publisher.
Likely cause is your AV software blocking the file.
Try saving it with -O innocent_name.exe
> ----
> wget https://cygwin.com/setup-x86_64.exe.sig
> wget https://cygwin.com/setup-x86_64.exe
> gpg --verify setup-x86_64.exe.sig setup-x86_64.exe
> gpg: Signature made Fri 09 Sep 2016 02:20:05 AM PDT using DSA key ID
> 676041BA
> gpg: Good signature from "Cygwin <cygwin@cygwin.com>"
-------^^^^^^^^^^^^^^
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg: There is no indication that the signature belongs to the owner.
> Primary key fingerprint: 1169 DF9F 2273 4F74 3AA5 9232 A9A2 62FF 6760
> 41BA
Did you copy-pasted wrong console output or what?
--
With best regards,
Andrey Repin
Thursday, September 29, 2016 00:12:02
Sorry for my terrible english...
--
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:[~2016-09-28 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 21:06 Thomas Sanders
2016-09-28 21:11 ` Wayne Porter
2016-09-29 2:29 ` Herbert Stocker
2016-09-29 18:40 ` Lee
2016-09-28 21:20 ` Andrey Repin
2016-09-29 0:05 ` Thomas Sanders [this message]
2016-09-29 5:40 ` Brian Inglis
2016-09-29 18:41 ` 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=B0BF22335C47694D8CF77683CF7C809C8451E60E@TWHQ-MAIL1.trellisware.com \
--to=tsanders@trellisware.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).