On 23 February 2016 at 07:34, Benedikt Ritter wrote:
> I'm confused. None of the other PMC members has expressed whether he or she
> want's the see Chimera/crypto joining Apache Commons, yet we're already
> discussing how JNI bindings should be handled.
>
> I'd like to see:
> 1) a clear statement
On 23/02/2016 09:12, sebb wrote:
> On 23 February 2016 at 07:34, Benedikt Ritter wrote:
>> I'm confused. None of the other PMC members has expressed whether he or she
>> want's the see Chimera/crypto joining Apache Commons, yet we're already
>> discussing how JNI bindings should be handled.
>>
>>
On Tue, Feb 23, 2016 at 12:14 AM, Colin P. McCabe wrote:
> Many CPUs come with built-in support for certain cryptographic and/or
> hash/checksum-related primitives. For example, modern x86 CPUs have
> CRC32C implemented in hardware. Currently, this must be accessed via
> inline assembly express
2016-02-23 10:18 GMT+01:00 Mark Thomas :
> On 23/02/2016 09:12, sebb wrote:
> > On 23 February 2016 at 07:34, Benedikt Ritter
> wrote:
> >> I'm confused. None of the other PMC members has expressed whether he or
> she
> >> want's the see Chimera/crypto joining Apache Commons, yet we're already
>
On Tue, Feb 23, 2016 at 10:47 AM, Benedikt Ritter wrote:
> I still have concerns about the IP, since this seems to be an Intel
> codebase. I do not have the necessary experience to say what would be the
> right way here. My gut feeling tells me, that we should go through the
> incubator. WDYT?
A
Hi all,
I got a quick look at the Chimera code. If I understand well it consists in:
- a native interface to the OpenSSL AES & secure random functions
- an abstraction layer to use the JCE or OpenSSL AES implementation
- an abstraction layer to use the JCE or OpenSSL secure random
- encrypting/dec
GitHub user dweiss opened a pull request:
https://github.com/apache/commons-compress/pull/8
COMPRESS-320: add the ability to quickly "skip" entries while scanning 7z
archive
As described in JIRA:
https://issues.apache.org/jira/browse/COMPRESS-320
You can merge this pull request
Thanks all for the valuable feedbacks and discussions.
Here are my replies for some of the questions..
[Mark wrote]
It depends. I care less about the quality of the code than I do about
the community that comes with it / forms around it. A strong community
can fix code issues. Great code can't save
On Tue, Feb 23, 2016 at 2:53 AM, Emmanuel Bourg wrote:
> Hi all,
>
> I got a quick look at the Chimera code. If I understand well it consists
> in:
> - a native interface to the OpenSSL AES & secure random functions
> - an abstraction layer to use the JCE or OpenSSL AES implementation
> - an abst
Yes, we have implementations for both JCE cipher and Openssl Cipher. It's
configurable for user.
-Original Message-
From: Jochen Wiedmann [mailto:jochen.wiedm...@gmail.com]
Sent: Tuesday, February 23, 2016 5:40 PM
To: Commons Developers List
Cc: Hadoop Common
Subject: Re: [crypto][chimer
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
>> 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
12 matches
Mail list logo