Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Tue, 15 Apr 2003 10:30:59 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: crypt... Message-ID: <20030415083059.GA5896@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <00b601c3028d$65a9d8a0$3f33fea9 AT HAPPYCOMPUTER> <20030414163247 DOT GB32658 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Tue, Apr 15, 2003 at 06:51:41AM +1000, Gareth Pearce wrote: > the gpl type licensing constraints or something else? (I would of imaginged > there was some bsd crypt out there that would satisfy the first?) (given the > level of availability of 56bit DES, I wouldnt of thought it was patent) AFAIR we were in trouble originally due to the US export problems (sic) of strong encryptions. Nobody today conciders 56bit DES a strong encryption but it's just a few years since the export restrictions were lightened. We were (and still are) careful not to taint Cygwin itself with export restricted code. But, after all, PTC, aren't they ;-) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/