From: Nick Lowe <nick.lowe@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Using Red Hat digital signing on setup.exe (was Re: Cygwin 1.7.14-2 setup.exe v2.772 broken?)
Date: Sun, 29 Apr 2012 00:54:00 -0000 [thread overview]
Message-ID: <CADSoG1sQdW8dwcFpc=CFLbRxU+391BbHHr1ronDF2SoyJHtqEA@mail.gmail.com> (raw)
In-Reply-To: <CADSoG1ss2n9Y8GpwEoYB1tFKXf5r3hL7cgRfCxTYooK+SFvCvw@mail.gmail.com>
I forgot to add, it also needs to be signed by a trusted root for it
to be useful to most people.
On Sun, Apr 29, 2012 at 1:51 AM, Nick Lowe <nick.lowe@gmail.com> wrote:
> "I installed 2.772 on my systems as soon as it was available and I
> don't see any such issue using my local mirror. Did you try another
> mirror?"
>
> Quite, but the idea of corruption was implicit in that question. A
> digital signature would rule that out. It was only a suggestion to
> ensure that that would never be a possibility.
>
> What's with the hostility? It's really bad etiquette... ;)
>
> Nick
--
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:[~2012-04-29 0:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 22:34 Cygwin 1.7.14-2 setup.exe v2.772 broken? Ken
2012-04-28 4:11 ` marco atzeri
2012-04-28 4:53 ` marco atzeri
2012-04-28 17:03 ` Ken
2012-04-28 18:06 ` Corinna Vinschen
2012-04-28 18:22 ` Nick Lowe
2012-04-28 20:50 ` Using Red Hat digital signing on setup.exe (was Re: Cygwin 1.7.14-2 setup.exe v2.772 broken?) Christopher Faylor
2012-04-28 20:57 ` Nick Lowe
2012-04-29 0:46 ` Christopher Faylor
2012-04-29 0:51 ` Nick Lowe
2012-04-29 0:54 ` Nick Lowe [this message]
2012-04-30 16:30 ` Larry Hall (Cygwin)
2012-04-30 16:34 ` Christopher Faylor
2012-04-30 17:41 ` Larry Hall (Cygwin)
2012-04-30 18:00 ` Nick Lowe
2012-04-28 18:24 ` Cygwin 1.7.14-2 setup.exe v2.772 broken? Christopher Faylor
2012-04-28 18:34 ` Ken
2012-04-28 20:45 ` Christopher Faylor
2012-04-28 21:02 ` marco atzeri
2012-04-29 21:02 ` Ken
2012-04-30 9:00 ` Achim Gratz
2012-04-30 16:30 ` Christopher Faylor
2012-04-30 18:00 ` Achim Gratz
2012-04-30 12:43 ` Nellis, Kenneth
2012-04-30 13:14 ` Earnie Boyd
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='CADSoG1sQdW8dwcFpc=CFLbRxU+391BbHHr1ronDF2SoyJHtqEA@mail.gmail.com' \
--to=nick.lowe@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).