Date: Tue, 20 Jun 1995 12:10:37 -0700 From: Timothy Moore <moore@WOLFE.net> To: paul@freebsd.org Cc: rgrimes@gndrsh.aac.dev.com, mark@grondar.za, FreeBSD-current@freebsd.org Subject: Re: DES, crypt and eBones Message-ID: <199506201910.MAA22919@gonzo.wolfe.net> In-Reply-To: Paul Richards's message of Tue, 20 Jun 1995 17:36:18 %2B0100 (BST) <199506201637.RAA05174@lambda>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Paul Richards <paul@lambda> Date: Tue, 20 Jun 1995 17:36:18 +0100 (BST) Reply-to: paul@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UK-ASCII Content-Transfer-Encoding: 8bit Content-Length: 1544 Sender: current-owner@freebsd.org In reply to Rodney W. Grimes who said > > I would rather just stay away from the Kerberos code... > This is just passing the buck though (and is relevant for the crypt code in general and not just kerberos). Either you (i.e. those in the US) import work that is based on a site outside the US or we (i.e outside the US) grab the work that you do and very clearly break the export laws. Basing the work at a site outside the US and importing it seems the better of the two. I agree with Poul, we should move the non-exportable code to a "safe" site and call it secure.freebsd.org. It can become an official distribution site that everyone can import from. I think you're missing something. It's just as serious a violation of the ITAR rules to import crypto stuff into the US as export it. It's a munition, it doesn't really matter what direction it gets shipped. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506201910.MAA22919>