X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <20120428205029.GB20709@ednor.casa.cgf.cx> References: <4F9B1EF7 DOT 1080501 AT comcast DOT net> <4F9B6DC1 DOT 3030303 AT gmail DOT com> <4F9B77B1 DOT 9070200 AT gmail DOT com> <4F9C22B1 DOT 5000405 AT comcast DOT net> <20120428180621 DOT GA23030 AT calimero DOT vinschen DOT de> <20120428205029 DOT GB20709 AT ednor DOT casa DOT cgf DOT cx> Date: Sat, 28 Apr 2012 21:57:01 +0100 Message-ID: Subject: Re: Using Red Hat digital signing on setup.exe (was Re: Cygwin 1.7.14-2 setup.exe v2.772 broken?) From: Nick Lowe To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes 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 > It's bad etiquette to derail an email thread with unrelated questions. I certainly didn't mean to derail it, the other points were ancillary to the implicit point that I intended to make which is that if the executable was digitally signed, any potential corruption would immediately be flagged by the operating system. -- 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