DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=f3T1tTrjcHU8vq4A
	fqkLzzWcHGZFU/pab3rGFN8izy7YyvRfel95YTLjWbFPbitH4KzaLdcd3H3HaOlR
	Lw8h11ggJGryQnETisKx3DHdxQmqZM9bDZUjWf7t/JU09Dl7T0tSWxWVUR4hxJ+q
	pRSphJcUeV4VywnLR/kiIIhAob4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 15 Dec 2016 11:57:19 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1514497430.20161215115719@yandex.ru>
To: Kal Sze <swordangel@gmail.com>, cygwin@cygwin.com
Subject: Re: Latest setup.exe not code-signed?
In-Reply-To: <CAGZiy71hduc-LZvLvqXWNzYpN7foKrvobVP5q3S=KeagukQAsg@mail.gmail.com>
References: <CAGZiy71hduc-LZvLvqXWNzYpN7foKrvobVP5q3S=KeagukQAsg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Kal Sze!

> It looks like the new setup-x86_64.exe is not code-signed? Is that on
> purpose? IIRC, the previous versions were code-signed.

No.

> Do we now only
> rely on the .sig signature file to verify it?

Been like that all the time.


-- 
With best regards,
Andrey Repin
Thursday, December 15, 2016 11:56:57

Sorry for my terrible english...


--
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