From owner-cvs-src@FreeBSD.ORG Mon Aug 9 18:44:37 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2900016A591 for ; Mon, 9 Aug 2004 18:44:37 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE85343D5F for ; Mon, 9 Aug 2004 18:44:36 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 487 invoked from network); 9 Aug 2004 18:44:36 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 9 Aug 2004 18:44:36 -0000 Received: from 10.50.40.208 (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i79IiDtK076097; Mon, 9 Aug 2004 14:44:32 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Mark Murray Date: Mon, 9 Aug 2004 11:14:58 -0400 User-Agent: KMail/1.6 References: <200408062200.i76M0tvk068161@grimreaper.grondar.org> In-Reply-To: <200408062200.i76M0tvk068161@grimreaper.grondar.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408091114.58674.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: src-committers@FreeBSD.org cc: cvs-src@FreeBSD.org cc: cvs-all@FreeBSD.org cc: Colin Percival cc: Colin Percival cc: Paul Richards 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 ... X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Aug 2004 18:44:37 -0000 On Friday 06 August 2004 06:00 pm, Mark Murray wrote: > 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. Hmm, we build the release for our "embedded" device using the FreeBSD release scripts and install using sysinstall config scripts. I don't think it is too much of a stretch to imagine that other people making appliances might do the same. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org