You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Julius Davies <ju...@cucbc.com> on 2006/08/23 07:03:51 UTC
commons-ssl - corporate CLA sent via courier
Hi,
Sorry to spam "apache@apache.org". Just a note that Credit Union Central Of British Columbia has sent two signed copies of the Corporate CLA via courier to:
The Apache Software Foundation,
1901 Munsey Drive,
Forest Hill, MD
21050-2747,
U.S.A.
This is regarding donation of the code currently listed here:
http://juliusdavies.ca/commons-ssl/
We've sent two signed copies. One is for your records, the other we need someone who can speak for Apache to sign and send back to us. We couriered it because we always courier contracts. You can send it back however you see fit (U.S. Postal Service is fine). Please send it back "Attention: Natalie Goncharova".
I've personally also mailed an "Invidivual CLA". I put it in a mailbox this evening through regular Canada Post. Should probably arrive in 2 weeks at the most. You don't have to send me back one of these. But please do send back a signed copy of the Corporate CLA!
------------------------------------
Sorry to httpclient-dev about the long delay on this. I went on a 3 week vacation shortly after my original email and just got too busy after that.
I have a new feature in "commons-ssl" since I last wrote:
- Works with Java 1.3 + JSSE
I also am very close to supporting standard "Apache" style ssleay format RSA keys, encrypted or plain PKCS-1. These are the same keys you create by following this FAQ:
http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#selfcert
I have some experimental code (not uploaded yet) that can handle the following types (with help from BouncyCastle's ASN parsing):
#1. RSA key - not encrypted!
-----BEGIN RSA PRIVATE KEY-----
MIICXgIBAAKBgQDiLwhut8clGGkLoGq86u+IMh8HE5YSwmWgC6QqlyBXcBrlK87p
[....]
#2. RSA key - encrypted!
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-CBC,[8-byte-binary-salt/iv]
#3. DEK-Info: DES-EDE3-CBC,[8-byte-binary-salt/iv]
#4. DEK-Info: AES-128-CBC,[16-byte-binary-salt/iv]
#5. DEK-Info: AES-192-CBC,[16-byte-binary-salt/iv]
#6. DEK-Info: AES-256-CBC,[16-byte-binary-salt/iv]
I'm going to create a formal "commons-ssl" project proposal. But I'm also going to be really tightly coupled to HTTPClient - CRL checking is going to be mostly supported through HTTPClient! So I'm wondering if maybe it should all just be part of "httpclient.jar".
If I do create a commons-ssl sub-project in the incubator, I'm wondering if Oleg or Sebb or anyone else here would like to join. Oleg - I'm especially indebted to you. Your httpclient-contrib examples were very very helpful to me and CUCBC these past two years. I've been using your "Auth" example in production for at least 1.5 years now.
yours,
Julius Davies
Senior Application Developer
Credit Union Central of British Columbia
http://juliusdavies.ca/
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: commons-ssl - corporate CLA sent via courier
Posted by Martin van den Bemt <ml...@mvdb.net>.
I'll keep an eye on it when it is received.
Did you run the code donation through the incubator to eg see if it needs a software grant ?
Mvgr,
Martin
Ortwin Glück wrote:
> Julius is referring to the following earlier post:
> http://mail-archives.apache.org/mod_mbox/jakarta-httpclient-dev/200605.mbox/%3c1146702335.4891.83.camel@apple.ca%3e
>
>
> I see no problem with the BouncyCastle license. We can include the
> library. As discussed earlier we can put the code into a separate
> subproject of HttpComponents.
>
> Julius, would you be so kind to notify us when the CLA has presumably
> reached Apache, so we can ask confirmation from the secretary? Thanks.
>
> Odi
>
> Julius Davies wrote:
>> Sorry to httpclient-dev about the long delay on this. I went on a 3
>> week vacation shortly after my original email and just got too busy
>> after that.
>>
>> I have a new feature in "commons-ssl" since I last wrote:
>>
>> - Works with Java 1.3 + JSSE
>>
>> I also am very close to supporting standard "Apache" style ssleay
>> format RSA keys, encrypted or plain PKCS-1. These are the same keys
>> you create by following this FAQ:
>>
>> http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#selfcert
>>
>> I have some experimental code (not uploaded yet) that can handle the
>> following types (with help from BouncyCastle's ASN parsing):
>>
>> #1. RSA key - not encrypted!
>> -----BEGIN RSA PRIVATE KEY-----
>> MIICXgIBAAKBgQDiLwhut8clGGkLoGq86u+IMh8HE5YSwmWgC6QqlyBXcBrlK87p
>> [....]
>>
>> #2. RSA key - encrypted!
>> -----BEGIN RSA PRIVATE KEY-----
>> Proc-Type: 4,ENCRYPTED
>> DEK-Info: DES-CBC,[8-byte-binary-salt/iv]
>>
>>
>> #3. DEK-Info: DES-EDE3-CBC,[8-byte-binary-salt/iv]
>>
>> #4. DEK-Info: AES-128-CBC,[16-byte-binary-salt/iv]
>>
>> #5. DEK-Info: AES-192-CBC,[16-byte-binary-salt/iv]
>>
>> #6. DEK-Info: AES-256-CBC,[16-byte-binary-salt/iv]
>>
>>
>> I'm going to create a formal "commons-ssl" project proposal. But I'm
>> also going to be really tightly coupled to HTTPClient - CRL checking
>> is going to be mostly supported through HTTPClient! So I'm wondering
>> if maybe it should all just be part of "httpclient.jar".
>>
>> If I do create a commons-ssl sub-project in the incubator, I'm
>> wondering if Oleg or Sebb or anyone else here would like to join.
>> Oleg - I'm especially indebted to you. Your httpclient-contrib
>> examples were very very helpful to me and CUCBC these past two years.
>> I've been using your "Auth" example in production for at least 1.5
>> years now.
>>
>>
>> yours,
>>
>> Julius Davies
>> Senior Application Developer
>> Credit Union Central of British Columbia
>>
>> http://juliusdavies.ca/
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: commons-ssl - corporate CLA sent via courier
Posted by Ortwin Glück <od...@odi.ch>.
Julius is referring to the following earlier post:
http://mail-archives.apache.org/mod_mbox/jakarta-httpclient-dev/200605.mbox/%3c1146702335.4891.83.camel@apple.ca%3e
I see no problem with the BouncyCastle license. We can include the
library. As discussed earlier we can put the code into a separate
subproject of HttpComponents.
Julius, would you be so kind to notify us when the CLA has presumably
reached Apache, so we can ask confirmation from the secretary? Thanks.
Odi
Julius Davies wrote:
> Sorry to httpclient-dev about the long delay on this. I went on a 3 week vacation shortly after my original email and just got too busy after that.
>
> I have a new feature in "commons-ssl" since I last wrote:
>
> - Works with Java 1.3 + JSSE
>
> I also am very close to supporting standard "Apache" style ssleay format RSA keys, encrypted or plain PKCS-1. These are the same keys you create by following this FAQ:
>
> http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#selfcert
>
> I have some experimental code (not uploaded yet) that can handle the following types (with help from BouncyCastle's ASN parsing):
>
> #1. RSA key - not encrypted!
> -----BEGIN RSA PRIVATE KEY-----
> MIICXgIBAAKBgQDiLwhut8clGGkLoGq86u+IMh8HE5YSwmWgC6QqlyBXcBrlK87p
> [....]
>
> #2. RSA key - encrypted!
> -----BEGIN RSA PRIVATE KEY-----
> Proc-Type: 4,ENCRYPTED
> DEK-Info: DES-CBC,[8-byte-binary-salt/iv]
>
>
> #3. DEK-Info: DES-EDE3-CBC,[8-byte-binary-salt/iv]
>
> #4. DEK-Info: AES-128-CBC,[16-byte-binary-salt/iv]
>
> #5. DEK-Info: AES-192-CBC,[16-byte-binary-salt/iv]
>
> #6. DEK-Info: AES-256-CBC,[16-byte-binary-salt/iv]
>
>
> I'm going to create a formal "commons-ssl" project proposal. But I'm also going to be really tightly coupled to HTTPClient - CRL checking is going to be mostly supported through HTTPClient! So I'm wondering if maybe it should all just be part of "httpclient.jar".
>
> If I do create a commons-ssl sub-project in the incubator, I'm wondering if Oleg or Sebb or anyone else here would like to join. Oleg - I'm especially indebted to you. Your httpclient-contrib examples were very very helpful to me and CUCBC these past two years. I've been using your "Auth" example in production for at least 1.5 years now.
>
>
> yours,
>
> Julius Davies
> Senior Application Developer
> Credit Union Central of British Columbia
>
> http://juliusdavies.ca/
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: commons-ssl - corporate CLA sent via courier
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Tue, 2006-08-22 at 22:03 -0700, Julius Davies wrote:
...
>
>
> I'm going to create a formal "commons-ssl" project proposal. But I'm also going to be really tightly coupled to HTTPClient - CRL checking is going to be mostly supported through HTTPClient! So I'm wondering if maybe it should all just be part of "httpclient.jar".
>
> If I do create a commons-ssl sub-project in the incubator, I'm wondering if Oleg or Sebb or anyone else here would like to join. Oleg - I'm especially indebted to you. Your httpclient-contrib examples were very very helpful to me and CUCBC these past two years. I've been using your "Auth" example in production for at least 1.5 years now.
>
Hi Julius,
Truth to be told, I feel rather overstretched with my existing
open-source commitments. Even though I am in favor of having the
commons-ssl project, I do not think i would be able to actively
contribute code to it. I can certainly participate in some way, mostly
at the high level, though, or in those areas that are HttpClient
related.
Please do go ahead and propose commons-ssl for incubation at Apache. I
believe several projects can be potentially interested: HttpComponents,
Commons Net, MINA. Do not feel discouraged if the idea fails to generate
enough support. We will certainly find home for most of your code within
Commons HttpClient / HttpComponents in that case.
Oleg
>
> yours,
>
> Julius Davies
> Senior Application Developer
> Credit Union Central of British Columbia
>
> http://juliusdavies.ca/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org