delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com> |
List-Archive: | <http://sourceware.cygnus.com/ml/cygwin-developers/> |
List-Post: | <mailto:cygwin-developers AT sourceware DOT cygnus DOT com> |
List-Help: | <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
Sender: | cygwin-developers-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin-developers AT sourceware DOT cygnus DOT com |
Date: | Mon, 14 Feb 2000 12:27:02 +0100 (MET) |
Message-Id: | <200002141127.MAA04961@burner.fokus.gmd.de> |
From: | schilling AT fokus DOT gmd DOT de |
To: | corinna AT vinschen DOT de, cygwin-developers AT sourceware DOT cygnus DOT com |
Subject: | Re: Can we include a crypt() package in cygwin now? |
>From: Corinna Vinschen <corinna AT vinschen DOT de> >Chris Faylor wrote: >> >> Does anyone know if the loosening of export restrictions will >> allow us to include a crypt() implementation in cygwin? >> >> cgf >Netscape exports it's 128-bit version now to us, too. So I think >it's no problem to include for example the standard 56 bit-DES for >a simple setkey(), encrypt(), crypt() implementation. Further >enhancements not excluded. >You know the joke: We already use that algorithms since they >are worldwide published in books... There aiso exists a German DIN standard for it ;-) Sorry, I cannot remember the number. If you like, I may look it up when I am home. Jörg EMail:joerg AT schily DOT isdn DOT cs DOT tu-berlin DOT de (home) Jörg Schilling D-13353 Berlin js AT cs DOT tu-berlin DOT de (uni) If you don't have iso-8859-1 schilling AT fokus DOT gmd DOT de (work) chars I am J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |