Date: Fri, 06 Aug 2004 23:00:55 +0100 From: Mark Murray <markm@FreeBSD.ORG> To: Paul Richards <paul@originative.co.uk> Cc: cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/bin/ed Makefile src/gnu/usr.bin/cvs/cvs Makefile src/kerberos5 Makefile.inc src/lib/libfetch Makefile src/lib/libpam/libpam Makefile src/lib/libpam/modules/pam_krb5 Makefile src/lib/libpam/modules/pam_ksu Makefile ... Message-ID: <200408062200.i76M0tvk068161@grimreaper.grondar.org> In-Reply-To: Your message of "Fri, 06 Aug 2004 21:49:08 BST." <1091825348.17455.19.camel@myrddin>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Richards writes: > It doesn't however follow that FreeBSD is always exempt from export > controls because it might not be if your exporting it as a product, even > if that product is just FreeBSD on a CD. This is just plain incorrect. If it is Open Source, it is exportable. > We'll always need to support > the ability to build non-crypto releases so that it can be safely > embedded in products that don't need crypto without encumbering the end > product with a requirement for an export license. We have the ability to build a NOCRYPT _world_. For people building appliances, that is sufficient. But people building appliances have control over the whole manufacturing process, and the crypto-nature of the product is therefore up to them. Open-source the OS on their product; no problem. Make it closed source and deal with export conditions. The ability to build NOCRYPT _releases_ is irrelevant. M -- Mark Murray iumop ap!sdn w,I idlaH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408062200.i76M0tvk068161>