public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: setup-x86.exe BAD signature from "Cygwin <cygwin@cygwin.com>"
Date: Tue, 18 Oct 2016 14:28:00 -0000	[thread overview]
Message-ID: <CAD8GWstNZhV70ykkCUz5XHoRgJw_EAY56-Mj74jJT=ZyC1YKiA@mail.gmail.com> (raw)
In-Reply-To: <B0BF22335C47694D8CF77683CF7C809C845476D1@TWHQ-MAIL2.trellisware.com>

On 10/17/16, Thomas Sanders wrote:
> Am I doing something wrong here?
>
> 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: BAD signature from "Cygwin <cygwin@cygwin.com>"
>
> If I am not doing something wrong, this has been going on for a few weeks.
> Please advise either way.

works for me
$ gpg --verify cygwinSetup-x86.exe.sig cygwinSetup-x86.exe
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/documentation/faqs.html for more
information
gpg: Signature made Fri Sep  9 05:20:02 2016 EDT 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

have you tried downloading from both home & work?  to different machines?

Lee

--
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

  reply	other threads:[~2016-10-17 22:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 22:54 Thomas Sanders
2016-10-18 14:28 ` Lee [this message]
2016-10-18 14:34 ` Brian Inglis
2016-10-18 14:35 ` Brian Inglis

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='CAD8GWstNZhV70ykkCUz5XHoRgJw_EAY56-Mj74jJT=ZyC1YKiA@mail.gmail.com' \
    --to=ler762@gmail.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).