X-Recipient: archive-cygwin@delorie.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.1080501@comcast.net>	<4F9B6DC1.3030303@gmail.com>	<4F9B77B1.9070200@gmail.com>	<4F9C22B1.5000405@comcast.net>	<20120428180621.GA23030@calimero.vinschen.de>	<CADSoG1tUY2BXCsU2UcnrgFPAg9KXFn2N5J4zcoi_MVJUQwb0Aw@mail.gmail.com>	<20120428205029.GB20709@ednor.casa.cgf.cx>
Date: Sat, 28 Apr 2012 21:57:01 +0100
Message-ID: <CADSoG1tVAHVoi3fCtXT+ZRpywJ2w_jcMXgCfoNVEaoLVPGA7JA@mail.gmail.com>
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 <nick.lowe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.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