Return-Path: X-Original-To: apmail-legal-discuss-archive@www.apache.org Delivered-To: apmail-legal-discuss-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8938CC701 for ; Mon, 17 Mar 2014 14:26:48 +0000 (UTC) Received: (qmail 28131 invoked by uid 500); 17 Mar 2014 14:26:33 -0000 Delivered-To: apmail-legal-discuss-archive@apache.org Received: (qmail 27621 invoked by uid 500); 17 Mar 2014 14:26:31 -0000 Mailing-List: contact legal-discuss-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: Reply-To: legal-discuss@apache.org List-Id: Delivered-To: mailing list legal-discuss@apache.org Received: (qmail 27604 invoked by uid 99); 17 Mar 2014 14:26:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2014 14:26:28 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [208.78.103.231] (HELO vorsha.objectstyle.org) (208.78.103.231) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 17 Mar 2014 14:26:21 +0000 Received: (qmail 19386 invoked from network); 17 Mar 2014 14:38:21 -0000 Received: from unknown (HELO ?192.168.1.39?) (212.98.191.4) by vorsha.objectstyle.org with SMTP; 17 Mar 2014 14:38:21 -0000 From: Andrus Adamchik Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Apache Cayenne adding data encryption - how to stay compliant Date: Mon, 17 Mar 2014 17:25:58 +0300 Message-Id: <8916E02D-0D7E-433F-A55D-0A6DC008D077@apache.org> Cc: private@cayenne.apache.org To: legal-discuss@apache.org Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) X-Mailer: Apple Mail (2.1874) X-Virus-Checked: Checked by ClamAV on apache.org Hi legal-discuss, 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 = =93encryption=94 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: "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.=94 So what is the current procedure? Thanks, Andrus [1] = http://mail-archives.apache.org/mod_mbox/cayenne-dev/201403.mbox/%3C3ED637= D3-CE95-46B6-B172-593B9EF31FC1%40objectstyle.org%3E [2] https://www.apache.org/dev/crypto.html= --------------------------------------------------------------------- To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org For additional commands, e-mail: legal-discuss-help@apache.org