From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Brian Inglis <Brian.Inglis@systematicsw.ab.ca>
Cc: cygwin@cygwin.com, dalestan@gmail.com
Subject: Re: Adding an embedded signature on setup-x86_64.exe
Date: Mon, 21 Nov 2022 13:49:30 +0100 [thread overview]
Message-ID: <Y3tz2pCZW1q6ZPCJ@calimero.vinschen.de> (raw)
In-Reply-To: <bbc8e50d-0445-65a2-8bf7-1a7671b5fefa@SystematicSw.ab.ca>
On Nov 20 13:45, Brian Inglis wrote:
> On Sun, 20 Nov 2022 17:17:18 +0000, Jon Turney wrote:
> > On 18/11/2022 21:15, Dale McCoy wrote:
> > > I use Cygwin in the course of work, and while I can use the external gpg
> > > signature to verify the validity of setup-x86_64.exe, my IT department
> > > can't see that step. They get somewhat concerned when they see that Windows
> > > thinks setup-x86_64.exe is unsigned, and I certainly don't blame them.
> > > Can I convince you to also embed a signature in the installer, so Windows
> > > recognizes the file is signed?
>
> > This something I'd like to do, but unfortunately, the remaining blocking
> > issues are not technical.
> >
> > In order to sign the code in this way, the key needs to be signed by a
> > CA that participates in Microsoft Trusted Root Program. These CAs
> > charge an annual fee. As the person who makes the setup releases, I'm
> > not going to pay that out of my own pocket, and we currently have no
> > organization to collect donations for that (or any other) purpose.
>
> If Cygwin becomes an SFC member, they may be able to fund Cygwin signing certs.
Good point!
Corinna
prev parent reply other threads:[~2022-11-21 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 21:15 Dale McCoy
2022-11-20 7:26 ` Brian Inglis
2022-11-20 8:46 ` Thomas Wolff
2022-11-20 18:37 ` Jon Turney
2022-11-21 12:53 ` Jon Turney
2022-11-20 17:17 ` Jon Turney
2022-11-20 20:45 ` Brian Inglis
2022-11-21 12:49 ` Corinna Vinschen [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=Y3tz2pCZW1q6ZPCJ@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=Brian.Inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=dalestan@gmail.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).