From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: dalestan@gmail.com
Subject: Re: Adding an embedded signature on setup-x86_64.exe
Date: Sun, 20 Nov 2022 00:26:39 -0700 [thread overview]
Message-ID: <5b5164e3-8003-d336-3778-836a1216f863@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAMU-TAuPF3DZPYe3xJ0F_GyrChZPRXjXbYAfD6tt9mY+a7j8kQ@mail.gmail.com>
On Fri Nov 18 21:15:04 GMT 2022, 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?
> I couldn't find a previous request on the mailing list for this, but I may
> have missed it in my attempts to grep the monthly digests.
See thread "Should cygwin's setup*.exe be signed using Sign Tool?":
https://cygwin.com/pipermail/cygwin/2015-April/220978.html
https://inbox.sourceware.org/cygwin/E1Ydjc5-0000kv-WD@rmm6prod02.runbox.com/
In case we ever need it, one of our setup maintainers packaged osslsigncode:
https://cygwin.com/packages/summary/osslsigncode-src.html
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2022-11-20 7:26 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 [this message]
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
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=5b5164e3-8003-d336-3778-836a1216f863@SystematicSw.ab.ca \
--to=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).