X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 17 Mar 2010 11:06:49 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: incomplete/corrupted setup.exe
Message-ID: <20100317150649.GA29284@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.58.1003171042591.9914@mail3.jubileegroup.co.uk>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 Wed, Mar 17, 2010 at 10:45:47AM +0000, G.W. Haywood wrote:
>On Tue, 16 Mar 2010 Csaba Raduly wrote:
>>>Perhaps the MD5 and/or SHA1 checksums for the current setup.exe should
>>>be published (and updated every time there's a new release) next to the
>>>download link (like Apache does, for example)
>>
>>It is however a very highly-desirable goal.  I'll try and find some
>>round tuits to see if we can't get some traction.
>
>That would be a very acceptable alternative to my original suggestion
>of renaming setup.exe each time it's (re)released, even if it's a bit
>more work for you.  :( Thanks.

To be clear, while Dave does seem to be implying that he has the ability
to make this happen, this really is basically my decision and the
decision of the other people who maintain the site, i.e., not Dave.  Any
actual work involved would likely be done by me.

I've floated the idea about getting a certificate to allow https access
to my fellow overseers and was largely met with yawns.  All of them are
involved with other significant projects hosted on sourceware.org and
have not noticed a need for this.

Since I haven't seen any guarantees that adding https would fix this
problem I'm not convinced that this justifies the amount of work
involved.  So, until the mailing list is flooded with people who can't
download setup.exe because we don't have https access, I am satisfied
with not doing anything.

cgf

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