X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Mail-Handler: MailHop Outbound by DynDNS X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18W3erxnhV/vLn8R/FrW4Vo Date: Sat, 9 Jun 2012 11:57:00 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Trusted Software Vendor Message-ID: <20120609155700.GA21988@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20120608184641 DOT GA13771 AT ednor DOT casa DOT cgf DOT cx> <4FD32DC5 DOT 10703 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FD32DC5.10703@gmail.com> 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: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Sat, Jun 09, 2012 at 01:04:37PM +0200, V?clav Zeman wrote: >On 06/08/2012 08:46 PM, Christopher Faylor wrote: >> On Fri, Jun 08, 2012 at 02:15:27PM -0400, Milton Quinteros S. wrote: >>>Would you consider the possibility to subscribe to the Comodo Trusted >>>Software Vendor list >>>(http://internetsecurity.comodo.com/trustedvendor/signup.php), and sign >>>every executable? It would be so useful for Comodo Firewall users. >>>Best regards. >>> >>>Milton Quinteros Salas >>1) Wrong mailing list. >> >>2) Do you have any idea how many executables are in the release? No. > >Well, that part sounds like it could be automated. I obviously know how to automate things. I also know that the Cygwin release doesn't all come from one place and package maintainers don't use just one way to produce packages. So, any automation would be complicated. You could theoretically push the burden onto cygwin.com itself but that would be a big change to the way that we do things now and I'm really not willing to burden cygwin.com with the cycles necessary to unpack tarballs at cygwin.com to sign them. 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