Message-ID: <4FD73CC9.3070501@etr-usa.com>
Date: Tue, 12 Jun 2012 06:57:45 -0600
From: Warren Young <warren@etr-usa.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Trusted Software Vendor
References: <!&!AAAAAAAAAAAYAAAAAAAAAH3PqnIBVHtCiVMVjN0ExZLigAAAEAAAAJXIkaLIcH5Pn+g+gRSa2KoBAAAAAA==@expertise.cl> <20120608184641.GA13771@ednor.casa.cgf.cx> <4FD32DC5.10703@gmail.com> <20120609155700.GA21988@ednor.casa.cgf.cx>
In-Reply-To: <20120609155700.GA21988@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 6/9/2012 9:57 AM, Christopher Faylor wrote:
>
>and I'm really
> not willing to burden cygwin.com with the cycles necessary to unpack
> tarballs at cygwin.com to sign them.

Based on the traffic I see to cygwin-apps, my sense is that this would 
amount to single-digit CPU-minutes per day, once you get through the 
initial conversion.  That can be nice'd to the point that it takes a 
month; this doesn't have to be a Big Bang conversion.

I think a much bigger problem is getting a Linux toolchain set up on the 
main package repo server that can sign these executables.  My Google-fu 
says the GNU tools have no idea how to do this today.

Then someone has to spend at least a few hours writing and testing the 
script to do all this.  It might take a person-day.

Red Hat might not have to buy a code signing cert for this.  They might 
already have one that will work: http://goo.gl/5Hm3C

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