d it now.
On 4 Jun 2016 11:35 a.m., "Benedikt Ritter" wrote:
> Chen, Haifeng schrieb am Fr., 3. Juni 2016 um
> 08:20 Uhr:
>
> > Thanks Stian, Dapeng and folks!
> >
> > For Commons Crypto, do we still have to wait for other process to
> > finish or we now
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/li
>> c enses/exports/index.page/eccnmatrix.xml
>>
?
Thanks for your help.
Haifeng
-Original Message-
From: Chen, Haifeng [mailto:haifeng.c...@intel.com]
Sent: Thursday, May 26, 2016 9:42 AM
To: Commons Developers List
Subject: RE: US Export classification & ECCN registration for encryption in
commons?
https://issues.apache.org/
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
016 3:36 PM
To: Commons Developers List
Subject: Re: US Export classification & ECCN registration for encryption in
commons?
Stian Soiland-Reyes schrieb am Mo., 23. Mai 2016 um
09:34 Uhr:
> On 23 May 2016 3:42 a.m., "Chen, Haifeng" wrote:
> >
> > So how about we
>> Are you sure this is the case for commons-crypto? I thought we only
>> supported JCE encryption and Open SSL encryption.
From the definition of "OCI", I tend to not consider Commons Crypto is an Open
cryptographic interface. The algorithm and key lengths it support are fixed.
I would tend to
toolkits, including
for operating systems and cryptographic service providers (CSPs). [740.17(b)(3)]
What folks think about this?
-Original Message-
From: Chen, Haifeng [mailto:haifeng.c...@intel.com]
Sent: Friday, May 20, 2016 1:28 PM
To: Commons Developers List
Subject: RE: US Exp
you are
designed to be used with OpenSSL and JCE, with links to them.
But note:
https://www.bis.doc.gov/index.php/policy-guidance/encryption/classification
Do any of those apply to Commons Crypto?
On 19 May 2016 at 07:45, Chen, Haifeng wrote:
> Hi Stian,
> I saw you worked active
Hi Stian,
I saw you worked actively on same registration issue for Taverna. Do you have
any suggestions on what steps we should take for Crypto registration?
We are keenly to get a first release of Crypto.
Regards,
Haifeng
-Original Message-
From: Chen, Haifeng [mailto:haifeng.c
extened a bit the concept (gold plating). The ideal thing is to create an
extension as you did at OpensslNative.c that supports pkcs11. Can i provide a
JIRA and do the same thing, maintaining the same interface?
Best Regards,
Giorgio
On Mon, May 16, 2016 at 5:09 AM, Chen, Haifeng
wrote:
>
Hi Zoppi,
The current API design of Commons Crypto basically follows the similar way of
the Cipher API and Stream API in java.
You mentioned another API style. I am not so familiar with HSM.
So the question is: Are there any specific reasons that Cipher style API cannot
be used for the implement
Hi folks,
From LEGAL-250 discussion, it showed that Commons Crypto should be registered.
Shall we also add Commons Crypto to ECCN Matrix in
http://www.apache.org/licenses/exports/ page (eccnmatrix.xml) the same as what
Apache Taverna did?
Regards,
Haifeng
-Original Message-
From: sebb [
Dear sir,
Commons Crypto is a new module in Apache Commons and we are preparing a the
first release.
Stian has pointed out there may be needed to do US Export classification & ECCN
registration [1]. I checked http://www.apache.org/dev/crypto.html page but not
sure about what steps we need to do
we want sooner. So
I suggest we can proceed the alpha release now.
Please feel free to share your opinion.
If there is no objection, we will proceed to prepare the release artifacts and
send out the release VOTE to the community when ready.
Regards,
Haifeng
From: Chen, Haifeng
Sent: Thursday
Hi,
After weeks of collaborated work from the community, the renaming, building,
API refactoring and documentation are almost done.
Much thanks to the Commons community for all your support.
The community folks to prepare an alpha release if we want sooner. So I suggest
we can proceed the alpha
: [CRYPTO] How to build CRYPTO on Mac OS 10.11?
Chen, Haifeng schrieb am Di., 3. Mai 2016 um
03:49 Uhr:
> Sorry to not response in the past days due to Holiday here.
> We will start to check that. I agree that JNA is a good thing to try
> as long as the performance impact is in an a
Sorry to not response in the past days due to Holiday here.
We will start to check that. I agree that JNA is a good thing to try as long as
the performance impact is in an acceptable level.
-Original Message-
From: sebb [mailto:seb...@gmail.com]
Sent: Monday, May 2, 2016 6:51 PM
To: Com
, 2016 7:24 PM, "Dan Tran" wrote:
> I would prefer all Commons projects using the same style :-) sorry
> can't help to making some noise :-)
>
> On Thu, Apr 28, 2016 at 7:09 PM, Chen, Haifeng
>
> wrote:
>
> > Mixed whitespace styles should be definite
> submission or it will be rejected. Getting it right in this first
> place will save you having to rewrite it.
>
> It says that we can continue with original coding format if we want.
> But anyway we can decide now.
>
>
>
> Regards,
> Uma
>
> On 4/26/16, 3:0
release sooner, marking release ALPHA tagged make sense IMO.
Regards,
Uma
On 4/25/16, 7:02 PM, "sebb" wrote:
>On 26 April 2016 at 02:56, Chen, Haifeng wrote:
>>>> Sounds like a tough time schedule. It's only one week until May.
>> Yeah, it's a tough time s
look at the commit history. Or are
you just using Jira as a to-do list in the early days of this component in its
new home in Apache Commons?
Gary
On Apr 25, 2016 6:47 PM, "Chen, Haifeng" wrote:
>>In our coding guidelines [1] we say that "The standard indentation is
>&
...@apache.org]
Sent: Tuesday, April 26, 2016 12:03 AM
To: Commons Developers List
Subject: Re: [CRYPTO] Switch from JNI to JNA
Chen, Haifeng schrieb am Mo., 25. Apr. 2016 um
08:38 Uhr:
> >> Maybe its an option to replace JNI by JNA [1]. This would have IHMO
> several advantages like
>
the JNA experiment and not release it.
Make sense.
Regards,
Haifeng
-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Tuesday, April 26, 2016 6:04 AM
To: Commons Developers List
Subject: Re: [CRYPTO] Switch from JNI to JNA
On Sun, Apr 24, 2016 at 11:38 PM, Ch
>>In our coding guidelines [1] we say that "The standard indentation is 4
>>spaces per indent - but respect the number of spaces used by the original."
>>The [crypto] Java code I've seen to far is all 2 spaces per indent.
>>I think now is the time to do this, most IDEs can do a one-shot format of
>> Maybe its an option to replace JNI by JNA [1]. This would have IHMO several
>> advantages like
>> * No C code needs to be written, compiled, tested and maintained
>> * Its easier compared to JNI (this could help attracting more people to
>> contribute)
>> * Many supported platforms [2], precom
tents. Maybe this helps.
Thanks,
Haifeng
-Original Message-
From: Chen, Haifeng [mailto:haifeng.c...@intel.com]
Sent: Friday, April 22, 2016 9:52 AM
To: Commons Developers List
Subject: RE: [CRYPTO] Git repository requested
Thanks Benedikt and Gary.
Will check that and get into our plannin
repo. Maybe Apache Commons Daemon can be
> an inspiration.
>
> BR,
> Benedikt
>
> Chen, Haifeng schrieb am Do., 21. Apr. 2016
> um
> 08:21 Uhr:
>
> > Hi folks,
> > The lock for CRYPTO git repository has been lifted. Thanks Gavin!
> > The community i
Hi folks,
The lock for CRYPTO git repository has been lifted. Thanks Gavin!
The community is starting to work toward the first release. Thank you all for
the support!
Regards,
Haifeng
-Original Message-
From: Chen, Haifeng
Sent: Thursday, April 21, 2016 2:07 PM
To: Commons Developers
s,
Haifeng
-Original Message-----
From: Chen, Haifeng [mailto:haifeng.c...@intel.com]
Sent: Wednesday, April 20, 2016 1:09 PM
To: Commons Developers List
Subject: RE: [CRYPTO] Git repository requested
Thanks Uma for the information. Yes, it should be already granted. We just need
to wait the lock to
: [CRYPTO] Git repository requested
Looks like access already has been granted. Please looks here if any one
missing. http://home.apache.org/phonebook.html?unix=commons
Regards,
Uma
On 4/19/16, 7:40 PM, "Chen, Haifeng" wrote:
>Thanks for the reminding. Confirmed that the code impor
write
access to Crypto repository or we need additional step to setup?
Regards,
Haifeng
-Original Message-
From: Benedikt Ritter [mailto:brit...@apache.org]
Sent: Tuesday, April 19, 2016 5:23 AM
To: Commons Developers List
Subject: Re: [CRYPTO] Git repository requested
Hi,
Chen, Haifeng
27 to the status
"Waiting for Infra", If you think it is necessary, please help to change.
Regards,
Haifeng
-Original Message-----
From: Chen, Haifeng [mailto:haifeng.c...@intel.com]
Sent: Monday, April 18, 2016 9:44 AM
To: Commons Developers List
Subject: RE: [CRYPTO] Git repos
should be able to
configure the project as you see fit.
Benedikt
Chen, Haifeng schrieb am Fr., 15. Apr. 2016 um
03:32 Uhr:
> Thanks Benedikt!
> My JIRA username is: jerrychenhf
>
> Regards,
> Haifeng
>
> -Original Message-
> From: Gangumalla, Uma [mailto:
username: umamaheswararao
Regards,
Uma
On 4/14/16, 5:55 AM, "Benedikt Ritter" wrote:
>Benedikt Ritter schrieb am Mi., 13. Apr. 2016 um
>11:09 Uhr:
>
>> Chen, Haifeng schrieb am Mi., 13. Apr. 2016
>> um
>> 05:18 Uhr:
>>
>>> The git reposito
The git repository for Apache Commons Crypto has been created. It is locked so
commits won't be accepted for now, will inform Daniel when we want the lock
lifted.
https://git-wip-us.apache.org/repos/asf?p=commons-crypto.git
Next we may need to setup a JIRA project and the initial committers.
Tha
Thanks Benedikt so much for your effort driving this and all folks for support.
The developers at the original github also made improvements towards Apache
Commons such as the API doc, user guide and site.
Haifeng
-Original Message-
From: Benedikt Ritter [mailto:brit...@apache.org]
Sen
Apache Commons Crypto
-Original Message-
From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com]
Sent: Tuesday, March 29, 2016 9:30 AM
To: Commons Developers List
Subject: Re: [DISCUSS][CHIMERA] Name for the new component
Just collected all the proposed names here for tracking purpose a
Thanks Uma for putting out the proposal.
And thanks to Benedikt and all the folks for your hearted support and
suggestions!
-Original Message-
From: Benedikt Ritter [mailto:brit...@apache.org]
Sent: Thursday, March 24, 2016 7:52 PM
To: Commons Developers List
Subject: [RESULT][VOTE] Acc
>> Any reason JNI cannot be replaced by JNA? (sorry for the hijack!)
We didn't try JNA. Technically, JNA should be working here. JNI is used
considering a few factors:
1. Keep the library dependency as light as we can, considering the JNI is a
relative thin layer and simple here.
2. Performance
Hi Sebb,
Thank you for raising the question.
The expertise point of view, the folks in the initial committer list is
committed to maintain the code, including Java and JNI code. From the community
point of view, it is open and it welcomes other committers and developers in
the community to suppo
+1 (non-binding)
-Original Message-
From: Benedikt Ritter [mailto:brit...@apache.org]
Sent: Monday, March 21, 2016 4:46 PM
To: Commons Developers List
Cc: Hadoop Common
Subject: [VOTE] Accept Chimera as new Apache Commons Component
Hi all,
after long discussions I think we have gathe
doption
of JDK9 will be much later than that time I guess.
Thanks,
Haifeng
-Original Message-
From: Emmanuel Bourg [mailto:ebo...@apache.org]
Sent: Friday, February 26, 2016 11:03 PM
To: Commons Developers List
Cc: common-...@hadoop.apache.org
Subject: Re: [crypto][chimera] Next steps
branch. And the branched code can be copied into Commons github as
final.
Thanks,
Haifeng
-Original Message-
From: Chen, Haifeng [mailto:haifeng.c...@intel.com]
Sent: Wednesday, February 24, 2016 12:40 PM
To: Commons Developers List
Cc: common-...@hadoop.apache.org
Subject: RE: [crypto
>> The same should be there with Chimera/Apache Crypto.
Yes, current implementation will fallback to JCE Cipher if native is not
available.
[Uma] we would fix up IP issues if any sooner. If you see all the code file
license header is with Apache License files.
The current repo and package struct
Thanks Bourg for these questions.
>> Sorry if it sounds naive, but why not accessing the OpenSSL functions
>> through a JCE provider instead of building an abstraction layer on top of
>> another abstraction layer (JCE). The Apache JuiCE project was an attempt to
>> implement this idea a few yea
Given the current scope and if we don't see significant value adding other
algorithms, Commons Crypto AES or Commons AES does be a better descriptive name.
Thanks,
Haifeng
-Original Message-
From: Chen, Haifeng
Sent: Monday, February 22, 2016 2:52 PM
To: Commons Developers
s
AES would be a better name.
Gary
On Sun, Feb 21, 2016 at 6:28 PM, Chen, Haifeng
wrote:
> Thanks Benedikt, Uma, Gary, Ole, and Emmanuel Bourg for your support!
> It's great to have Chimera to be part of Apache Commons.
>
> >>[ Emmanuel Bourg] Define the scope of the proj
Thanks Benedikt, Uma, Gary, Ole, and Emmanuel Bourg for your support! It's
great to have Chimera to be part of Apache Commons.
>>[ Emmanuel Bourg] Define the scope of the project? Do we go after Bouncy
>>Castle and aim for an equivalent feature set?
Agree to make a clear scope of the project. T
Thanks Benedikt for your support!
>> I'm no crypto expert but I can help with the Apache Commons related tasks,
>> like moving the code over to Apache Commons, setting up the maven build,
>> publishing the project website etc.
This is really great help.
>> 1. There are no Apache sub communitie
49 matches
Mail list logo
