[112151] in cryptography@c2.net mail archive
Re: Question on export issues
daemon@ATHENA.MIT.EDU (Florian Weimer)
Wed Jan 2 11:40:01 2008
From: Florian Weimer <fw@deneb.enyo.de>
To: Ivan =?utf-8?Q?Krsti=C4=87?= <krstic@solarsail.hcs.harvard.edu>
Cc: dan@geer.org, "Alan" <alan@clueserver.org>, cryptography@metzdowd.com
Date: Tue, 01 Jan 2008 22:34:23 +0100
In-Reply-To: <784F986E-570E-4F5F-809B-E3F776104263@solarsail.hcs.harvard.edu>
("Ivan =?utf-8?Q?Krsti=C4=87=22's?= message of "Sun, 30 Dec 2007 18:48:13
-0500")
* Ivan Krsti=C4=87:
> We've recently had to jump through the BIS crypto export hoops at
> OLPC. Our systems both ship with crypto built-in and, due to their
> Fedora underpinnings, allow end-user installation of various crypto
> libraries -- all open-source -- through our servers. It was a
> nightmare; the regulations and paperwork appear to be designed for the
> use case of individual applications that utilize a handful of
> primitives and attempt to keep the user from examining or modifying
> the utilized crypto. Trying to fit a Linux distribution into this
> model proved, er, challenging.
Debian has been filing notices for crypto export for years (at BXA for
some time; nowadays, it's likely BIS). So far, nobody there has
complained that what is being done is insufficient.
Here are some details: <http://www.debian.org/legal/cryptoinmain>
The actual process may have changed a bit over the years.
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.com
