Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: legal-discuss@apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Apache Cayenne adding data encryption - how to stay compliant
From: Andrus Adamchik <aadamchik@apache.org>
In-Reply-To: 
 <CAM1oqKpZRy22i1rs8fpUrwPc4uouiqKtR5kNLtKn70G0AWW+qQ@mail.gmail.com>
Date: Wed, 19 Mar 2014 09:08:00 +0300
Cc: legal-discuss@apache.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <A11B5709-7272-4CE5-94A2-377B233CD582@apache.org>
References: <8916E02D-0D7E-433F-A55D-0A6DC008D077@apache.org>
 <CAM1oqKpZRy22i1rs8fpUrwPc4uouiqKtR5kNLtKn70G0AWW+qQ@mail.gmail.com>
To: private@cayenne.apache.org

Thanks Kevan. I guess we=92ll follow the precedent described on the =
site, unless someone else tells us not to.

Andrus


On Mar 19, 2014, at 2:00 AM, Kevan Miller <kevan.miller@gmail.com> =
wrote:

> On Mon Mar 17 2014 at 7:26:34 AM, Andrus Adamchik =
<aadamchik@apache.org>
> wrote:
>=20
>> Hi legal-discuss,
>>=20
>> We (the Apache Cayenne project) are working on a pluggable =
transparent
>> mechanism that will allow users to store certain columns in RDBMS in =
an
>> encrypted form [1]. The basic code is already committed (using ROT13
>> "encryption" as a proof of concept), and now we are approaching a =
point
>> when we write the code that will manage real ciphers using JCE (Java
>> Cryptography Extension) API. Cayenne itself will not contain any
>> cryptographic algorithms per se, but it will be specifically designed =
to
>> work with such algorithms provided by Java.
>>=20
>> So what do we need to do to stay compliant with US export =
regulations? I
>> am checking the relevant page on our site [2], which has this note:
>>=20
>> "the regulations covering US export control laws for encryption were
>> changed on June 25th 2010. This page describes the previous process. =
Until
>> an updated version has been drawn up and approved by the Apache VP =
Legal
>> Affairs, projects should check with the legal-discuss list before
>> proceeding."
>>=20
>> So what is the current procedure?
>>=20
>=20
> IIRC, the last several requests have been passed by Sam to counsel. =
And the
> response has always been follow the process described on that web =
page. Not
> sure if Jim wants to follow a different process...
>=20
> I don't know why that page was updated in the first place and I'm not
> really up-to-speed with export control laws.
>=20
> --kevan


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