From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: setup-x86.exe BAD signature from "Cygwin <cygwin@cygwin.com>"
Date: Tue, 18 Oct 2016 14:35:00 -0000 [thread overview]
Message-ID: <2c210134-64b8-cb32-8648-8c43aa50408b@SystematicSw.ab.ca> (raw)
In-Reply-To: <B0BF22335C47694D8CF77683CF7C809C845476D1@TWHQ-MAIL2.trellisware.com>
On 2016-10-17 14:20, 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.
> Thanks!
Try:
$ gpg --recv-keys 676041BA
$ gpg --edit-key 676041BA
gpg> trust
pub 1024D/676041BA created: 2008-06-13 expires: never usage: SC
trust: ultimate validity: ultimate
sub 1024g/A1DB7B5C created: 2008-06-13 expires: never usage: E
[ultimate] (1). Cygwin <cygwin@cygwin.com>
Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)
1 = I don't know or won't say
2 = I do NOT trust
3 = I trust marginally
4 = I trust fully
5 = I trust ultimately
m = back to the main menu
Your decision? 5
Do you really want to set this key to ultimate trust? (y/N) y
pub 1024D/676041BA created: 2008-06-13 expires: never usage: SC
trust: ultimate validity: ultimate
sub 1024g/A1DB7B5C created: 2008-06-13 expires: never usage: E
[ultimate] (1). Cygwin <cygwin@cygwin.com>
gpg> q
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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
prev parent reply other threads:[~2016-10-18 14:34 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
2016-10-18 14:34 ` Brian Inglis
2016-10-18 14:35 ` Brian Inglis [this message]
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=2c210134-64b8-cb32-8648-8c43aa50408b@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).