Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <009601c1fdb6$25b55300$c23fa8c0@transarc.ibm.com> From: "Michael Young" To: References: Subject: Re: PGP signatures for packages? Date: Fri, 17 May 2002 11:18:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >That's it. But without that I will not sign setup.exe. Just like I > > didn't compress it until UPX became a package :]. OK. I was hoping that you might treat this as a post-build distribution step, and might allow the use of non-Cygwin tools (much the way a developer might use a non-Cygwin text editor prior to building). Nobody else should be attempting to reproduce this result (that is, sign with *your* key). But I admire your self-hosting philosophy, so I'll leave it at that. Would you be willing to provide the binary over HTTPS? It looks like Apache with mod_ssl is built for Cygwin. Thanks again! -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.3 iQA/AwUBPOUfQlMkvpTT8vCGEQKiewCfdYpp3s780bFZsXaSYsXNt/1cOnwAn3sd mh3myzhL6PwUFvCnotlq9NWj =NAk0 -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/