On Feb 21, 2016 11:59 PM, "Benedikt Ritter" wrote:
>
> Hi again,
>
> 2016-02-20 12:15 GMT+01:00 Benedikt Ritter :
>
> > Hi,
> >
> > I'd like to discuss the next steps for moving the Chimera component to
> > Apache Commons. So far, none of the other PMC members has expressed his
or
> > her thoughts
Hi Gary,
We use JNI to get to Openssl.
Ferd
-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Monday, February 22, 2016 2:57 PM
To: Commons Developers List
Subject: Re: [crypto][chimera] Next steps
Curious: How to you get to OpenSSL, JNI? JNA?
Gary
On Sun, Fe
On Sun, 21 Feb 2016, Gary Gregory wrote:
Curious: How to you get to OpenSSL, JNI? JNA?
I know that Tomcat has done quite a bit of work around pulling in OpenSSL
in order to do SNI and ALPN. Mark Thomas gave a good talk on it at
ApacheCon last year, slides are at:
http://events.linuxfoundatio
I would highly recommend shading this library when it is used in
Hadoop and/or Spark, to prevent version skew problems between Hadoop
and Spark like we have had in the past.
What is the strategy for handling JNI components? I think at a
minimum, we should include the version number in the native
On Mon, Feb 22, 2016 at 6:28 PM, Colin P. McCabe wrote:
> What is the strategy for handling JNI components?
Wrong question, IMO. Should better be: What are the reasons for using
JNI components? Couldn't they be replaced? If so, that would very much
enhance the long term prospects of crypto|chime
>I would highly recommend shading this library when it is used in
Hadoop and/or Spark, to prevent version skew problems between Hadoop
and Spark like we have had in the past.
[uma]Ha. This avoids multiple jars versions issues. Agreed IMO.
>I think at a
minimum, we should include the version number
All files should follow the Commons Maven naming scheme to make it easy to
reach from Maven, Ivy and so on.
This will be commons-crypto-1.0.jar for example.
Gary
On Mon, Feb 22, 2016 at 1:06 PM, Gangumalla, Uma
wrote:
> >I would highly recommend shading this library when it is used in
> Hadoop
>All files should follow the Commons Maven naming scheme to make it easy to
>reach from Maven, Ivy and so on.
>This will be commons-crypto-1.0.jar for example.
Sure. Thanks Gary. We will follow the naming convention here from Commons.
Regards,
Uma
On 2/22/16, 1:20 PM, "Gary Gregory" wrote:
>Al
On Mon, Feb 22, 2016 at 1:26 PM, Gangumalla, Uma
wrote:
>
> >All files should follow the Commons Maven naming scheme to make it easy to
> >reach from Maven, Ivy and so on.
> >This will be commons-crypto-1.0.jar for example.
> Sure. Thanks Gary. We will follow the naming convention here from Commo
All,
I already sent something similar to the private security list
(secur...@apache.org) earlier this month and it was suggested that I post it to
the dev list for discussion.
There is a Java deserialization "gadget" in the commons-beanutils library that
can be used along with others in the JRE
Re-sending the references since the formatting and links seemed to have gotten
a bit messed up.
Further references:
Beanutils gadget chain:
https://gist.github.com/frohoff/9eb8811761ff989b3ac0
AppSecCali Marshalling Pickles Talk:
http://www.slideshare.net/frohoff1/appseccali-2015-marshallin
Hi Jochen,
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 expressed in JNI. It is worth it... at least in the
case of c
Checksum via JNI should be done in the commons-codec project.
Gary
On Feb 22, 2016 3:14 PM, "Colin P. McCabe" wrote:
> Hi Jochen,
>
> Many CPUs come with built-in support for certain cryptographic and/or
> hash/checksum-related primitives. For example, modern x86 CPUs have
> CRC32C implemented
Not a big fan of introducing JNI-based library to Commons. I'm -0
On Sat, Feb 20, 2016 at 6:15 AM Benedikt Ritter wrote:
> Hi,
>
> I'd like to discuss the next steps for moving the Chimera component to
> Apache Commons. So far, none of the other PMC members has expressed his or
> her thoughts ab
We already have commons-daemon that has C bits.
Gary
On Feb 22, 2016 3:27 PM, "James Carman" wrote:
> Not a big fan of introducing JNI-based library to Commons. I'm -0
>
> On Sat, Feb 20, 2016 at 6:15 AM Benedikt Ritter
> wrote:
>
> > Hi,
> >
> > I'd like to discuss the next steps for moving th
Still not a fan. My vote stands
On Mon, Feb 22, 2016 at 6:37 PM Gary Gregory wrote:
> We already have commons-daemon that has C bits.
>
> Gary
> On Feb 22, 2016 3:27 PM, "James Carman"
> wrote:
>
> > Not a big fan of introducing JNI-based library to Commons. I'm -0
> >
> > On Sat, Feb 20, 2016 a
All,
I already sent something similar to the private security list (
secur...@apache.org) earlier this month and it was suggested that I post it
to the dev list for discussion.
There is a Java deserialization "gadget" in the commons-beanutils library
that can be used along with others in the JRE
On 22 February 2016 at 23:43, James Carman wrote:
> Still not a fan. My vote stands
I'm inclined to agree with James here.
> On Mon, Feb 22, 2016 at 6:37 PM Gary Gregory wrote:
>
>> We already have commons-daemon that has C bits.
Have you tried building it?
>>
>> Gary
>> On Feb 22, 2016 3:27
At this point, it has just Java interfaces only.
-Original Message-
From: Colin P. McCabe [mailto:cmcc...@apache.org]
Sent: Tuesday, February 23, 2016 1:29 AM
To: Hadoop Common
Cc: Commons Developers List
Subject: Re: [crypto][chimera] Next steps
I would highly recommend shading this lib
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 whether Chimera/crypto should become part of Apache
Commons. Do w
20 matches
Mail list logo
