X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=Hz+7xbkwniRz0KiVqaCI40Guk1pKY9
	HdFGk5boG+eYOQC+5rYSLyYP+gURRNaEOU/pSwadF/I7Ps5RmHVxmDRb5MxDDPcS
	+9fPMJjdNOo43X8beucKArYDRfdB2TeoEN2gVOFgGGRJpY0T3D+4bbHh+VLL2jbN
	XTIoMkUKARUn4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; s=default; bh=pL/jDwfcYELUwNRGD2b5MVAeXTs=; b=RO76
	nbihfUWmiHOzkOU7BUjxQQmi83t5aLVlWvHrj/Sh188e0hEDvrJd0ri131guMVoU
	c7UE/orv2vmanfZFgWVQyKLk89hXtV2UbOu6oJZGTzWTnqy0VfRhCAaUHTAsCJlz
	XkXbNTePoWNZdtcO1YsRTSaCa3TwMX9QtmK474o=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.7 required=5.0 tests=AWL,BAYES_50,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: =?UTF-8?B?UmVuw6kgQmVyYmVy?= <r DOT berber AT computer DOT org>
Subject: Re: Should cygwin's setup*.exe be signed using Sign Tool?
Date: Thu, 09 Apr 2015 08:43:00 -0500
Lines: 23
Message-ID: <mg5vnn$ca8$1@ger.gmane.org>
References: <E1Ydjc5-0000kv-WD AT rmm6prod02 DOT runbox DOT com> <55267923 DOT 7070601 AT dronecode DOT org DOT uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0
In-Reply-To: <55267923.7070601@dronecode.org.uk>
X-IsSubscribed: yes

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