Date: Sun, 02 May 1999 16:58:29 +0200 From: Mark Murray <mark@grondar.za> To: Eivind Eklund <eivind@FreeBSD.ORG> Cc: freebsd-security@FreeBSD.ORG Subject: Re: Blowfish/Twofish Message-ID: <199905021458.QAA02696@greenpeace.grondar.za> In-Reply-To: Your message of " Sun, 02 May 1999 14:49:06 %2B0200." <19990502144906.E23950@bitbox.follo.net> References: <21634.925539195@critter.freebsd.dk> <Pine.BSF.3.96.990501150648.2670B-100000@fledge.watson.org> <19990502144906.E23950@bitbox.follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Eivind Eklund wrote: > On Sat, May 01, 1999 at 03:07:30PM -0400, Robert Watson wrote: > > So I'd gladly write this code, as well as do a number of other > > crypto-related things, but I'm inside the US. Someone outside the US will > > have to take this initiative, I'm afraid. > > For this application, being inside the US is probably not a problem. > The way I would implement this is to use OpenSSL (formerly SSLeay) > through their library interface, dlopen() the library, and only > support Blowfish passwords if the library is available. As what > you'll be writing is authentication infrastructure, not encryption > infrastructure, exporting it is not a problem. I do not know of any > country that forbid export of authentication infrastructure. _Way_ overkill. A far simpler structure can easily be built by hand. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905021458.QAA02696>