From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-announce@cygwin.com
Subject: Re: Cygwin setup signing public key update
Date: Sun, 7 Jun 2020 16:06:43 +0100 [thread overview]
Message-ID: <2af2ac56-cfe5-ce9a-4840-69927193effd@dronecode.org.uk> (raw)
In-Reply-To: <73cab308-f9a9-7a9b-bc92-d5d9180c7153@dronecode.org.uk>
On 13/03/2020 16:34, Jon Turney wrote:
> On 13/03/2020 16:13, Jon Turney wrote:
>> This is an announcement of an update to the key used to sign (i)
>> Cygwin setup executables, and (ii) the (compressed) setup.ini package
>> manifest.
>
> If you just run setup, and update it when it tells you to update it, no
> action is required, and this message chain will be of limited interest
> to you.
>
> This update is following the policy announced at [1]:
>
> > On 05/08/2008 14:30, Dave Korn wrote:
> >> If we, from time to time, need to change this key, we will release
> >> a new version of setup.exe and make announcements on the cygwin
> >> and cygwin-announce mailing lists, and on the cygwin.com website.
>
> Also see that post for further discussion of the technicals details of
> setup signing.
>
> The transition period, during which signatures are made using both keys
> will probably be approx. 90 days, circumstances permitting.
As of today, the signature made is not compatible with setup versions
<=2.894, and thus they will no longer work.
next prev parent reply other threads:[~2020-06-07 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6312.65287972695$1584116184@news.gmane.org>
2020-03-13 16:34 ` Jon Turney
2020-06-07 15:06 ` Jon Turney [this message]
2020-03-13 16:13 Jon Turney
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=2af2ac56-cfe5-ce9a-4840-69927193effd@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-announce@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).