setup.exe bad signatures?
Achim Gratz
Stromeko@nexgo.de
Wed Feb 26 19:50:00 GMT 2014
Michael Ryan writes:
> I'm trying to verify the signatures on the latest setup.exe files and I'm finding that they don't match:
>
> $ gpg --verify setup-x86.exe.sig
> gpg: Signature made Fri 13 Dec 2013 17:24:37 GMT using DSA key ID 676041BA
> gpg: BAD signature from "Cygwin <Cygwin AT cygwin.com>"
> $ gpg --verify setup-x86_64.exe.sig
> gpg: Signature made Fri 13 Dec 2013 17:38:14 GMT using DSA key ID 676041BA
> gpg: BAD signature from "Cygwin <cygwin AT cygwin.com>"
> $ md5sum setup-x86*
> 93ee19b4143133ec0d9462a27e5c92cb setup-x86_64.exe
> 2f2d2a21916b164c9f844810ada0f5f5 setup-x86_64.exe.sig
> 9b3e9b26fa040763f2673cc3dc0cf229 setup-x86.exe
> 3afb815ce823e601f999de777ea72885 setup-x86.exe.sig
>
> Am I doing something wrong, or...?
Probably not, those signatures are still referring to the previous
setup.exe files if you believe the date.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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
More information about the Cygwin
mailing list