This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Should cygwin's setup*.exe be signed using Sign Tool?
- From: Renà Berber <r dot berber at computer dot org>
- To: cygwin at cygwin dot com
- Date: Thu, 09 Apr 2015 08:43:00 -0500
- Subject: Re: Should cygwin's setup*.exe be signed using Sign Tool?
- Authentication-results: sourceware.org; auth=none
- References: <E1Ydjc5-0000kv-WD at rmm6prod02 dot runbox dot com> <55267923 dot 7070601 at dronecode dot org dot uk>
On 4/9/2015 8:05 AM, Jon TURNEY wrote:
[snip]
> The actual work that needs to be done here is to identify an alternative
> open source signing tool and how to use it.
>
> It would be nice to have such a tool packaged for cygwin, as that would
> allow people to sign any MinGW-w64 executables they make...
I've been using osslsigncode for a long time.
Ref: http://sourceforge.net/projects/osslsigncode/
It used to compile OTB in Cygwin (as well as Linux), depends on OpenSSL,
and libcurl.
But that was version 1.5.2.
The current version, 1.7.1, which on the way added "support for
compiling and running on Windows" messed things up (the usual way,
assuming that it is compiling for native Windows). I fix it by
disabling HAVE_WINDOWS_H in the generated config.h .
--
Renà Berber
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple