X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,WEIRD_PORT X-Spam-Check-By: sourceware.org Message-ID: <4BA1BA09.7040104@gmail.com> Date: Thu, 18 Mar 2010 05:28:41 +0000 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: incomplete/corrupted setup.exe References: <1268766945.5263.ezmlm@cygwin.com> <20100317150649.GA29284@ednor.casa.cgf.cx> <4BA17A9F.2000808@monai.ca> In-Reply-To: <4BA17A9F.2000808@monai.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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 > 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 cheers, DaveK -- 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