From: Jon Turney <jon.turney@dronecode.org.uk>
To: Dale McCoy <dalestan@gmail.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Adding an embedded signature on setup-x86_64.exe
Date: Sun, 20 Nov 2022 17:17:18 +0000 [thread overview]
Message-ID: <64eb894e-0bce-2e68-3e8b-a8cd69711514@dronecode.org.uk> (raw)
In-Reply-To: <CAMU-TAuPF3DZPYe3xJ0F_GyrChZPRXjXbYAfD6tt9mY+a7j8kQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2022-11-20 17:17 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 [this message]
2022-11-20 20:45 ` Brian Inglis
2022-11-21 12:49 ` 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=64eb894e-0bce-2e68-3e8b-a8cd69711514@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).