From owner-freebsd-questions@FreeBSD.ORG Thu Oct 7 03:25:50 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABA68106566B for ; Thu, 7 Oct 2010 03:25:50 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6FCEB8FC0A for ; Thu, 7 Oct 2010 03:25:50 +0000 (UTC) Received: by gyg4 with SMTP id 4so135718gyg.13 for ; Wed, 06 Oct 2010 20:25:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.101.138.6 with SMTP id q6mr235593ann.222.1286421949198; Wed, 06 Oct 2010 20:25:49 -0700 (PDT) Received: by 10.220.188.3 with HTTP; Wed, 6 Oct 2010 20:25:49 -0700 (PDT) X-Originating-IP: [128.95.133.175] In-Reply-To: References: <86fwwjyurd.fsf@red.stonehenge.com> <20101006215345.1a57c45c@gumby.homeunix.com> <86pqvnxbre.fsf@red.stonehenge.com> <20101006174309.407e4216@scorpio> <86d3rnxadh.fsf@red.stonehenge.com> Date: Wed, 6 Oct 2010 20:25:49 -0700 Message-ID: From: Rob Farmer To: Michael Powell Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: Like it or not, Theo has a point... freebsd is shipping export-restricted software in the core X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Oct 2010 03:25:50 -0000 On Wed, Oct 6, 2010 at 20:04, Michael Powell wrote= : > I was under the impression that the most onerous of these export rules an= d > restrictions applied to crypto technology. If this is so, what I don't qu= ite > grasp is what do crypto export restrictions have to do with acpi? Is acpi= a > copyrighted, patented, or trademark otherwise owned by some entity? Quite > possibly so as it is in contrib. I just have no idea who might "own" it. = Or > how it would fall afoul of crypto export restrictions. > > Looking forward to enlightenment. =A0:-) I'm not a lawyer either, so take all this with a grain of salt. Basically, there are two reasons the US will block an export, which you can read about at: http://www.bis.doc.gov/licensing/exportingbasics.htm 1) The export is considered "dangerous" for one reason or another, and needs to be licensed so the government can keep track of who is getting it and why they want it. Examples include military equipment, nuclear equipment, controlled substances, firearms, etc. Crypto is defined as a "munition" and is restricted for this reason. There are a lot of opinions about whether this is "right", but it has held up in court. 2) The destination is "designated as supporting terrorist activities" or is embargoed for political reasons (socialist/totalitarian government - Cuba, Iran, North Korea, Sudan, and Syria). Most of the people in these countries don't have access to a computer and the rights to install whatever they want on it, so this is targeted at government officials. As such, you are correct that for the vast majority of cases, the ACPI code shouldn't have problems or need a license. The biggest legal risk I can see is if ftp.freebsd.org and such allow people in the embargoed countries to download code - I've seen a brief reference saying Sourceforge was forced to IP ban these. --=20 Rob Farmer