RE: [CRYPTO] Suggestion from ApacheCON: Have a look at Amazon s2n

Hi Benedikt, I've took a glance at s2n. It is not a full replacement for OpenSSL, its crypto is a wrapper of OpenSSL. It doesn't support all the algorithms that OpenSSL supports. For instance, s2n does not support AES-CTR algorithm. Regards, Xianda -Original Message- From: Benedikt

RE: [Crypto] GCM pull request

Hi folks, I had a glance at the implementation of GCM Acceleration in HotSpot(Java 9) and did benchmark months ago. The implementation in HotSpot(Java 9) is not well optimized. Yes, there is an optimization opportunity for Java 9... AES-GCM(JDK8): 3.98 MB/s AES-GCM(JDK9): 267.78 M

RE: [CRYPTO] Feedback from ApacheCON Europe

ntions checking cpuid features with no indication as to when this instruction was added. On 23 November 2016 at 20:48, Ke, Xianda wrote: > Hi Benedict, > > >>1) Why does Commons Crypto implement it's own Crypto API instead of > providing a JCE provider? > Dapeng has answer

RE: [CRYPTO] Feedback from ApacheCON Europe

Hi Benedict, >>1) Why does Commons Crypto implement it's own Crypto API instead of providing >>a JCE provider? Dapeng has answered the question. Here are some additional details The deployment of JCE provider is tedious for big data user who owns thousands of nodes. (a). copy jar to java-home,

RE: [VOTE] Release CRYPTO 1.0.0 based on RC1

+1 (non-binding) Verified locally, UT passed. Regards, Xianda -Original Message- From: Sun, Dapeng [mailto:dapeng@intel.com] Sent: Tuesday, July 26, 2016 11:25 AM To: Commons Developers List Subject: [VOTE] Release CRYPTO 1.0.0 based on RC1 Hi all, Apache Commons CRYPTO was estab

RE: [VOTE] Release CRYPTO 1.0.0 based on RC1

Hi Jörg, I guess that the two warnings were caused by the permission of java.io.tmpdir (/tmp ). Crypto extracts *.so to java.io.tmpdir(or commons-crypto.tempdir). Try adding exec permission. Regards, Xianda -Original Message- From: Jörg Schaible [mailto:joerg.schai...@gmx.de] Sent:

RE: [CRYPTO] is the ConfigurationKeys class needed?

+1 Long long names is burden for user. What's more, following two constants are just for implementation. It does not make sense to mix these with the configuration keys. In fact, user can configure a buffer size or algorithm, but he cannot configure the default value. ConfigurationKeys.STREAM_

RE: [CRYPTO] Documenting the public API before it is too late...

Thanks sebb for the feedback. All the implementation classes shouldn't public. we are working on this. A JIRA (CRYPTO-71) was already created for the cipher implementation classes. We will continue. Regards, Xianda -Original Message- From: sebb [mailto:seb...@gmail.com] Sent: Wednesda