X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 	tests=AWL,BAYES_00,WEIRD_PORT
X-Spam-Check-By: sourceware.org
X-Cloudmark-SP-Filtered: true
X-Cloudmark-SP-Result: v=1.0 c=1 a=aCRlMrwmDrwA:10 a=VphdPIyG4kEA:10 a=8nJEP1OIZ-IA:10  a=zk19hA/YTAL+guUbg/dVXQ==:17 a=w_pzkKWiAAAA:8 a=Gz7s5_CCAAAA:8  a=FcoHsQnsM2flQuM1H2cA:9 a=eZaqbNZPNzRZVEv0yb1ONNteonIA:4 a=wPNLvfGTeEIA:10  a=TRvmKqLbH9UA:10
Message-ID: <4BA2CCA1.4090306@monai.ca>
Date: Thu, 18 Mar 2010 18:00:17 -0700
From: Steven Monai <steve+cygwin AT monai DOT ca>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: incomplete/corrupted setup.exe
References: <1268766945 DOT 5263 DOT ezmlm AT cygwin DOT com>  <Pine DOT LNX DOT 4 DOT 58 DOT 1003171042591 DOT 9914 AT mail3 DOT jubileegroup DOT co DOT uk> <20100317150649 DOT GA29284 AT ednor DOT casa DOT cgf DOT cx> <4BA17A9F DOT 2000808 AT monai DOT ca> <4BA1BA09 DOT 7040104 AT gmail DOT com>
In-Reply-To: <4BA1BA09.7040104@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

On 2010/03/17 10:28 PM, Dave Korn wrote:
> On 18/03/2010 00:58, Steven Monai wrote:
> 
>> As an alternative to setting up SSL on cygwin.com, what about the idea
>> of crypto-signing (e.g. with gnupg) every release of setup.exe, and then
>> posting the signature alongside the binary? I know I would breathe a
>> little easier if I were able to positively verify the authenticity of a
>> given setup.exe binary.
> 
>   That much is already done, and documented on the front page of cygwin.com:
> read the first sentence under "Installing and Updating Cygwin and its
> Packages" heading just beneath the mid-bar, or go straight to
> http://cygwin.com/setup.exe.sig

Ah, there it is. I don't know how I managed to miss that.

>> The public key would need to be distributed via channels other than just
>> cygwin.com, to make it more difficult to spoof. Fortunately, there are a
>> number of public PGP/GPG key servers to fill that purpose.
> 
>   And we have already uploaded it to them; DSA key ID 676041BA:
> 
> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0xA9A262FF676041BA

Fantastic! Thanks.

-SM
--

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