You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Tim Wild <ti...@solnetsolutions.co.nz> on 2004/05/25 06:28:24 UTC
client certificates: contribution
Hi,
I have a simple class that i've created that deals with client
certificates, based on the sample sun code, which i'd like to
contribute. It'd work fine for simple applications, and would be a good
starting point for more complex client cert requirements. Should I
contribute this, and if so, how would I go about contributing it?
Cheers
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
Re: client certificates: contribution
Posted by Oleg Kalnichevski <ol...@apache.org>.
Tim,
Just a few things to add to what Mike has said
(1) CLA is required only if you would like to be attributed the
authorship of the contributed code. Apache, as many other open-source
project, got a little stricter about code contributions these days due
to IP related legal problems in the Linux kernel space.
(2) I have been long planing to provide a version of HTTPS protocol
factory supporting client certificate authentication. I'll happily
review your code and see that it eventually gets committed to the CVS,
once everyone is happy with the implementation. Go ahead and open a
feature request with Bugzilla, attach your code, and I'll get back to
you with some feedback
Cheers
Oleg
On Tue, 2004-05-25 at 14:45, Michael Becke wrote:
> Tim,
>
> I would actually suggest creating a new bug in Bugzilla and attaching
> the contribution there. That way there is a public record of where the
> code came from.
>
> As Ortwin mentions a CLA, though actually not required, would be
> desirable.
>
> Mike
>
> On May 25, 2004, at 2:51 AM, Ortwin Glück wrote:
>
> >
> >
> > Tim Wild wrote:
> >> I was thinking more the cvs contrib directory, how would I get it in
> >> there?
> >
> > Tim,
> >
> > you would need write access to CVS (i.e. be a committer to the
> > HttpClient) project to directly import your code. Best is, to send
> > your code to one of the committers, as the list tends to strip
> > attachments off ones emails. To accept contributed code it is also
> > required that you file a CLA [1] with the ASF.
> >
> > [1] CLA: http://www.apache.org/licenses/index.html#clas
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > commons-httpclient-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> > commons-httpclient-dev-help@jakarta.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
Re: client certificates: contribution
Posted by Michael Becke <be...@u.washington.edu>.
Tim,
I would actually suggest creating a new bug in Bugzilla and attaching
the contribution there. That way there is a public record of where the
code came from.
As Ortwin mentions a CLA, though actually not required, would be
desirable.
Mike
On May 25, 2004, at 2:51 AM, Ortwin Glück wrote:
>
>
> Tim Wild wrote:
>> I was thinking more the cvs contrib directory, how would I get it in
>> there?
>
> Tim,
>
> you would need write access to CVS (i.e. be a committer to the
> HttpClient) project to directly import your code. Best is, to send
> your code to one of the committers, as the list tends to strip
> attachments off ones emails. To accept contributed code it is also
> required that you file a CLA [1] with the ASF.
>
> [1] CLA: http://www.apache.org/licenses/index.html#clas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> commons-httpclient-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
Re: client certificates: contribution
Posted by Ortwin Glück <or...@nose.ch>.
Tim Wild wrote:
> I was thinking more the cvs contrib directory, how would I get it in there?
Tim,
you would need write access to CVS (i.e. be a committer to the
HttpClient) project to directly import your code. Best is, to send your
code to one of the committers, as the list tends to strip attachments
off ones emails. To accept contributed code it is also required that you
file a CLA [1] with the ASF.
[1] CLA: http://www.apache.org/licenses/index.html#clas
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
Re: client certificates: contribution
Posted by Tim Wild <ti...@solnetsolutions.co.nz>.
I was thinking more the cvs contrib directory, how would I get it in there?
bagas wrote:
>IMHO .. Yes you should contribute this.
>
>Would you just send it in mail attachment for a while?
>
>
>-----Original Message-----
>From: Tim Wild [mailto:tim.wild@solnetsolutions.co.nz]
>Sent: Tuesday, May 25, 2004 11:28 AM
>To: commons-httpclient-dev@jakarta.apache.org
>Subject: client certificates: contribution
>
>Hi,
>
>I have a simple class that i've created that deals with client
>certificates, based on the sample sun code, which i'd like to
>contribute. It'd work fine for simple applications, and would be a good
>starting point for more complex client cert requirements. Should I
>contribute this, and if so, how would I go about contributing it?
>
>Cheers
>
>Tim
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail:
>commons-httpclient-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail:
>commons-httpclient-dev-help@jakarta.apache.org
>
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org
RE: client certificates: contribution
Posted by bagas <ba...@indoartha.co.id>.
IMHO .. Yes you should contribute this.
Would you just send it in mail attachment for a while?
-----Original Message-----
From: Tim Wild [mailto:tim.wild@solnetsolutions.co.nz]
Sent: Tuesday, May 25, 2004 11:28 AM
To: commons-httpclient-dev@jakarta.apache.org
Subject: client certificates: contribution
Hi,
I have a simple class that i've created that deals with client
certificates, based on the sample sun code, which i'd like to
contribute. It'd work fine for simple applications, and would be a good
starting point for more complex client cert requirements. Should I
contribute this, and if so, how would I go about contributing it?
Cheers
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail:
commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail:
commons-httpclient-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org