From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 4/4] Codesign setup.exe (DO NOT APPLY)
Date: Mon, 12 Dec 2016 18:47:00 -0000 [thread overview]
Message-ID: <87shptass0.fsf@Rainer.invalid> (raw)
In-Reply-To: <20161212173051.GD3705@calimero.vinschen.de> (Corinna Vinschen's message of "Mon, 12 Dec 2016 18:30:51 +0100")
Corinna Vinschen writes:
>> 2/ The signature should be timestamped, so that it remains vaild after the
>> signing key expires, but I assume you have to use the timestamp service of
>> the CA that signed the key.
>
> Not necessarily. We can workaround that by getting a new key and
> release a new setup.
That wouldn't do any good for folks trying to use an old setup version
or am I missing something?
In the meantime, we could provide a detached signature with the cygwin
key, just like we do for setup.ini?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2016-12-12 18:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 13:30 [PATCH setup 0/4] Various setup patches Jon Turney
2016-12-12 13:30 ` [PATCH setup 3/4] Remove unused grammar for dependent package architecture information Jon Turney
2016-12-12 13:30 ` [PATCH setup 4/4] Codesign setup.exe (DO NOT APPLY) Jon Turney
2016-12-12 17:31 ` Corinna Vinschen
2016-12-12 18:47 ` Achim Gratz [this message]
2016-12-13 8:30 ` Corinna Vinschen
2016-12-13 18:33 ` Achim Gratz
2016-12-13 20:01 ` Corinna Vinschen
2016-12-13 14:36 ` Jon Turney
2016-12-12 13:30 ` [PATCH setup 2/4] Fully initialize PROPSHEETPAGE Jon Turney
2016-12-12 13:30 ` [PATCH setup 1/4] Use English button labels 'Keep', 'Current' and 'Test' Jon Turney
2016-12-12 17:25 ` [PATCH setup 0/4] Various setup patches Corinna Vinschen
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=87shptass0.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@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).