Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Received-SPF: pass (athena.apache.org: domain of ben@reser.org designates
 192.242.17.19 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50EDBB0F.5040301@collab.net>
References: <50EDBB0F.5040301@collab.net>
Date: Wed, 9 Jan 2013 11:02:40 -0800
Message-ID: 
 <CADkdwvTEQsc-ZJpbPs-FTYiHHxJzY0kXTDqOvZVdfC=AbRtUEw@mail.gmail.com>
Subject: Re: Subversion, encryption, export restrictions, etc.
From: Ben Reser <ben@reser.org>
To: "C. Michael Pilato" <cmpilato@collab.net>
Cc: legal-discuss@apache.org,
	Subversion Full Committers <private@subversion.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jan 9, 2013 at 10:46 AM, C. Michael Pilato <cmpilato@collab.net> wrote:
> Some time ago, I (and other Subversion devs) began some work toward adding
> support in Apache Subversion for an encrypted authenication credentials
> store -- basically, a client-side place to stuff login creds used for
> accessing Subversion servers.  Along the way, I started wondering if this
> work would fall under the restrictions placed on export of software by the
> U.S.  I got some IANAL-type advice to the effect that our usage was fine and
> uncontrolled/unrestricted, but I'd really rather that we have our i's dotted
> and t's crossed on this.

One detail that may be important here is that there is no actual
encryption code in Apache Subversion, but rather but calls into the
encryption code that APR has.

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org