[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: sha-256 comment in /trunk/subversion/libsvn_subr/crypto.c

From: Ben Reser <ben_at_reser.org>
Date: Wed, 9 Jan 2013 09:32:37 -0800

On Wed, Jan 9, 2013 at 6:39 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> My state concern about our export status has, IIRC, been refuted. But I
> need to find documentation of that refutation, and then remember to update
> the wiki.

I'm guessing that your concern here is with US export restrictions.
Incidentally, just committing the code to the ASF repo would be export
since it's mirrored to Europe. However, I believe you qualify under
ECCN 5D002 and TSU exception in EAR 740.13(e).

Apache has a page covering this:

> Removing the code from trunk is fine, I suppose -- just means that when I
> next update my branch a bunch of supporting code will get blown away there,
> forcing me to re-add it. But that's no big deal. That kind of churn seems
> a bit unnecessary -- it is private, unused code after all.

Now that I think about it, I don't think it really matters if it is in
trunk or branch or a released code (by our definition) or not. The
rules are the same either way. So it's fine to leave it as far as I'm
concerned. Someone just needs to do the footwork to comply.
Received on 2013-01-09 18:33:15 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.