commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stian Soiland-Reyes <st...@apache.org>
Subject Re: US Export classification & ECCN registration for encryption in commons?
Date Sat, 04 Jun 2016 10:58:56 GMT
I'll start a separate thread for VFS classification as it has a bit
more dependencies.. :)

On 2 June 2016 at 20:58, Benedikt Ritter <britter@apache.org> wrote:
> If you know how so get this right for VFS, go for it!
>
> Stian Soiland-Reyes <stain@apache.org> schrieb am Do., 2. Juni 2016 um
> 16:35:
>
>> Thanks! It's already on https://www.apache.org/licenses/exports/
>>
>> I've added to the Commons Crypto README:
>>
>> https://github.com/apache/commons-crypto#export-restrictions
>>
>> (if changing, modify this text in pom.xml <description> and regenerate
>> README.md)
>>
>>
>> Shall I add VFS2 as well? Then Gary can send a joint notification message.
>>
>>
>>
>>
>> On 1 June 2016 at 03:01, Sun, Dapeng <dapeng.sun@intel.com> wrote:
>> > Thank Stian for your review!
>> >
>> >>We also need a second <Version> for the (future) source/binary
>> distributions with ControlledSource href=
>> https://www.apache.org/dist/commons/crypto/ - you would need to duplicate
>> the OpenSSL and JavaSE <ControlledSource> for that. See other examples in
>> the XML file.
>> > Thank you for pointing it out, we should add it.
>> >
>> >> is it 1.0.0 we're targeting for the first Commons Crypto release?
>> > Yes, 1.0.0 would be the first release.
>> >
>> > I have updated the staging website.
>> http://www.staging.apache.org/licenses/exports/index.html
>> >
>> >
>> > Regards
>> > Dapeng
>> >
>> > -----Original Message-----
>> > From: Stian Soiland-Reyes [mailto:stain@apache.org]
>> > Sent: Tuesday, May 31, 2016 6:45 PM
>> > To: Commons Developers List
>> > Subject: Re: US Export classification & ECCN registration for encryption
>> in commons?
>> >
>> > Thanks! Looks good.
>> >
>> > We also need a second <Version> for the (future) source/binary
>> distributions with ControlledSource href=
>> https://www.apache.org/dist/commons/crypto/ - you would need to duplicate
>> the OpenSSL and JavaSE <ControlledSource> for that. See other examples in
>> the XML file.
>> >
>> > In the second Version you can say <Names>1.0.0 and later</Names>
- is it
>> 1.0.0 we're targeting for the first Commons Crypto release?
>> >
>> > On 31 May 2016 at 11:03, Sun, Dapeng <dapeng.sun@intel.com> wrote:
>> >> Thank Stian and Haifeng, I have updated the file at my cms workspace.
>> >> If the change is okay for you, I will try to commit it to
>> >> http://www.staging.apache.org/licenses/exports/
>> >>
>> >> Index: trunk/content/licenses/exports/index.page/eccnmatrix.xml
>> >> ===================================================================
>> >> --- trunk/content/licenses/exports/index.page/eccnmatrix.xml
>> (revision 1655892)
>> >> +++ trunk/content/licenses/exports/index.page/eccnmatrix.xml
>> (working copy)
>> >> @@ -212,6 +212,25 @@
>> >>      </Version>
>> >>    </Product>
>> >>    <Product>
>> >> +    <Name>Apache Commons Crypto</Name>
>> >> +    <Version>
>> >> +      <Names>development</Names>
>> >> +      <ECCN>5D002</ECCN>
>> >> +      <ControlledSource href="
>> https://git-wip-us.apache.org/repos/asf/commons-crypto.git">
>> >> +        <Manufacturer>ASF</Manufacturer>
>> >> +        <Why>designed for use with encryption library</Why>
>> >> +      </ControlledSource>
>> >> +      <ControlledSource href="http://www.openssl.org/source/">
>> >> +        <Manufacturer>The OpenSSL Project</Manufacturer>
>> >> +        <Why>general-purpose cryptography library included with
>> OpenSSL</Why>
>> >> +      </ControlledSource>
>> >> +      <ControlledSource href="
>> http://www.oracle.com/technetwork/java/javase/downloads/index.html">
>> >> +        <Manufacturer>Oracle</Manufacturer>
>> >> +        <Why>general-purpose cryptography library (JCE) included
with
>> Java</Why>
>> >> +      </ControlledSource>
>> >> +    </Version>
>> >> +  </Product>
>> >> +  <Product>
>> >>      <Name>Apache Commons OpenPGP</Name>
>> >>      <Version>
>> >>        <Names>development</Names>
>> >>
>> >>
>> >> Regards
>> >> Dapeng
>> >>
>> >> -----Original Message-----
>> >> From: Stian Soiland-Reyes [mailto:stain@apache.org]
>> >> Sent: Monday, May 30, 2016 5:20 PM
>> >> To: Commons Developers List
>> >> Subject: RE: US Export classification & ECCN registration for
>> encryption in commons?
>> >>
>> >> I think we are good to continue as a "normal" 5D002 self-classification.
>> >>
>> >> Great if you will have a go, let me know if you would like me to help
>> or review!
>> >>
>> >> See http://www.apache.org/dev/crypto.html#sources for svn details,
>> >> linking to
>> >> https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/lic
>> >> enses/exports/index.page/eccnmatrix.xml
>> >>
>> >> I found just being a committer was enough to update the svn, after
>> >> which it should be live on
>> >> http://www.staging.apache.org/licenses/exports/
>> >>
>> >> If that works fine, then any ASF member can publish it using
>> >> https://cms.apache.org/ for the main website (it can be a bit slow)
>> >>
>> >> Normally it is the PMC Chair that sends the registration email after
>> that.
>> >> On 30 May 2016 8:09 a.m., "Chen, Haifeng" <haifeng.chen@intel.com>
>> wrote:
>> >>
>> >> Hi Stian,
>> >> If we decide to go ECCN 5D002 self-classify category, do you have an
>> idea that what I can proceed next?
>> >>
>> >> I saw you updated eccnmatrix.xml file for Taverna. Would you please
>> help share where is the place of the file and who has the privilege to make
>> an similar update for Commons Crypto?
>> >>
>> >> Thanks for your help.
>> >>
>> >> Haifeng
>> >>
>> >>
>> >> -----Original Message-----
>> >> From: Chen, Haifeng [mailto:haifeng.chen@intel.com]
>> >> Sent: Thursday, May 26, 2016 9:42 AM
>> >> To: Commons Developers List <dev@commons.apache.org>
>> >> Subject: RE: US Export classification & ECCN registration for
>> encryption in commons?
>> >>
>> >> https://issues.apache.org/jira/browse/LEGAL-256 is created and
>> commented to track this.
>> >>
>> >> If we think this analysis makes sense, we will choose to go ECCN 5D002
>> self-classify category. Will wait for a few days for feedbacks.
>> >>
>> >> Regards,
>> >> Haifeng
>> >>
>> >> -----Original Message-----
>> >> From: Chen, Haifeng [mailto:haifeng.chen@intel.com]
>> >> Sent: Tuesday, May 24, 2016 3:57 PM
>> >> To: Commons Developers List <dev@commons.apache.org>
>> >> Subject: RE: US Export classification & ECCN registration for
>> encryption in commons?
>> >>
>> >> Thanks Stian and Benedikt!
>> >>
>> >>> Let's create a Jira issue to track the categorisation process.
>> >> Do you mean to create a JIRA in LEGAL similar to LEGAL-250 to track
>> this?
>> >>
>> >>
>> >> Regards,
>> >> Haifeng
>> >>
>> >> -----Original Message-----
>> >> From: Benedikt Ritter [mailto:britter@apache.org]
>> >> Sent: Monday, May 23, 2016 3:36 PM
>> >> To: Commons Developers List <dev@commons.apache.org>
>> >> Subject: Re: US Export classification & ECCN registration for
>> encryption in commons?
>> >>
>> >> Stian Soiland-Reyes <stain@apache.org> schrieb am Mo., 23. Mai 2016
um
>> >> 09:34 Uhr:
>> >>
>> >>> On 23 May 2016 3:42 a.m., "Chen, Haifeng" <haifeng.chen@intel.com>
>> wrote:
>> >>> >
>> >>> > So how about we go to the process of ECCN 5D002 self-classify
>> >>> > category
>> >>> and registration like Taverna did?
>> >>>
>> >>> Agree on your evaluation, so ECCN 5D002 is good. This makes things a
>> >>> lot easier! :)
>> >>>
>> >>> Let's create a Jira issue to track the categorisation process.
>> >>>
>> >>
>> >> +1! good work everybody.
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> >> For additional commands, e-mail: dev-help@commons.apache.org
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> >> For additional commands, e-mail: dev-help@commons.apache.org
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> >> For additional commands, e-mail: dev-help@commons.apache.org
>> >
>> >
>> >
>> > --
>> > Stian Soiland-Reyes
>> > Apache Taverna (incubating), Apache Commons
>> > http://orcid.org/0000-0001-9842-9718
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > For additional commands, e-mail: dev-help@commons.apache.org
>> >
>>
>>
>>
>> --
>> Stian Soiland-Reyes
>> Apache Taverna (incubating), Apache Commons
>> http://orcid.org/0000-0001-9842-9718
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>



-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons
http://orcid.org/0000-0001-9842-9718

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message