You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Moran Jacuel <mo...@arx.com> on 2011/11/14 14:59:52 UTC

Changes in mod_ssl

Hello,

Our company is an HSM manufacturer (See link for http://www.arx.com/products/private-server-hsm PrivateServer product)
We wanted to connect apache server with SSL using our HSM to hold the Private RSA and Certificate.

We downloaded apache httpd-2.2.20 and modified the module mod_ssl that came with the package in a generic way to work with OpenSSL PKCS#11 engine.
Now we want to add the small code changes we made to the open source code.

It is not clear to us if the mod_ssl is part of the Apache project or not.
If so, can you please explain us who we need to contact and what is the procedure we need to follow.

Regards

Moran Jacuel | Software Engineer | ARX
phone: +972.3.9279512  | email: moranj@arx.com<bl...@arx.com> | www.arx.com<blocked::blocked::http://www.arx.com/////n>

RE: Changes in mod_ssl

Posted by "Plüm, Rüdiger, VF-Group" <ru...@vodafone.com>.
mod_ssl is part of Apache Http Server 2.0.x and up. Just open a report in bugzilla and attach the patch as a proposed enhancement.
Further discussion on this patch might happen there or here (depending on the contents of the discussion).
 
Regards
 
Rüdiger


________________________________

	From: Moran Jacuel [mailto:moranj@arx.com] 
	Sent: Montag, 14. November 2011 15:00
	To: dev@httpd.apache.org
	Cc: Moshe Harel
	Subject: Changes in mod_ssl
	
	

	Hello,

	 

	Our company is an HSM manufacturer (See link for http://www.arx.com/products/private-server-hsm PrivateServer product)

	We wanted to connect apache server with SSL using our HSM to hold the Private RSA and Certificate.

	 

	We downloaded apache httpd-2.2.20 and modified the module mod_ssl that came with the package in a generic way to work with OpenSSL PKCS#11 engine.

	Now we want to add the small code changes we made to the open source code.

	 

	It is not clear to us if the mod_ssl is part of the Apache project or not. 

	If so, can you please explain us who we need to contact and what is the procedure we need to follow. 

	 

	Regards

	Moran Jacuel | Software Engineer | ARX
	phone: +972.3.9279512  | email: moranj@arx.com <bl...@arx.com>  | www.arx.com <blocked::blocked::http://www.arx.com/////n>

Re: Changes in mod_ssl

Posted by Rainer Jung <ra...@kippdata.de>.
Hello Moran,

On 15.11.2011 14:54, Moran Jacuel wrote:
> Hello Rainer,
>
> I found out that the patch that I used in order to connect apache server with SSL using our HSM to hold the Private RSA and Certificate already exists in bugzilla at:
>
> https://issues.apache.org/bugzilla/show_bug.cgi?id=42687
>
> We found out that this patch works well. We would like to insert it in to the open source code.
>
> What is the status of this patch and what can I do in order to insert the patch to open source code?

It is better to contact the dev list and inquire about this patch there. 
A friendly nagging sometimes helps.

Regards,

Rainer

RE: Changes in mod_ssl

Posted by Moran Jacuel <mo...@arx.com>.
Hello Rainer, 

I found out that the patch that I used in order to connect apache server with SSL using our HSM to hold the Private RSA and Certificate already exists in bugzilla at:

https://issues.apache.org/bugzilla/show_bug.cgi?id=42687

We found out that this patch works well. We would like to insert it in to the open source code. 

What is the status of this patch and what can I do in order to insert the patch to open source code?

Regards, 

Moran Jacuel | Software Engineer | ARX
phone: +972.3.9279512  | email: moranj@arx.com | www.arx.com 


-----Original Message-----
From: Rainer Jung [mailto:rainer.jung@kippdata.de] 
Sent: Monday, November 14, 2011 4:56 PM
To: dev@httpd.apache.org
Cc: Moran Jacuel; Moshe Harel
Subject: Re: Changes in mod_ssl

Hello,

On 14.11.2011 05:59, Moran Jacuel wrote:
> Hello,
>
> Our company is an HSM manufacturer (See link for
> http://www.arx.com/products/private-server-hsm PrivateServer product)
>
> We wanted to connect apache server with SSL using our HSM to hold the
> Private RSA and Certificate.
>
> We downloaded apache httpd-2.2.20 and modified the module mod_ssl that
> came with the package in a generic way to work with OpenSSL PKCS#11 engine.
>
> Now we want to add the small code changes we made to the open source code.
>
> It is not clear to us if the mod_ssl is part of the Apache project or not.
>
> If so, can you please explain us who we need to contact and what is the
> procedure we need to follow.

Yes, mod_ssl for the Apache web server 2.x is part of the Apache web 
server project.

Some notes about contributing patches are available at:

http://httpd.apache.org/dev/patches.html

For a substantial contribution we would need a signed Contributor 
License Agreement (CLA), see

http://www.apache.org/licenses/#clas

In order to document the availability of a patch and track its use, I 
suggest you open a bugzilla issue and attach the patch there:

https://issues.apache.org/bugzilla/

For a bigger patch you can also discuss the patch on this list before or 
after opening the bugzilla issue.

Regards,

Rainer

Re: Changes in mod_ssl

Posted by Rainer Jung <ra...@kippdata.de>.
Hello,

On 14.11.2011 05:59, Moran Jacuel wrote:
> Hello,
>
> Our company is an HSM manufacturer (See link for
> http://www.arx.com/products/private-server-hsm PrivateServer product)
>
> We wanted to connect apache server with SSL using our HSM to hold the
> Private RSA and Certificate.
>
> We downloaded apache httpd-2.2.20 and modified the module mod_ssl that
> came with the package in a generic way to work with OpenSSL PKCS#11 engine.
>
> Now we want to add the small code changes we made to the open source code.
>
> It is not clear to us if the mod_ssl is part of the Apache project or not.
>
> If so, can you please explain us who we need to contact and what is the
> procedure we need to follow.

Yes, mod_ssl for the Apache web server 2.x is part of the Apache web 
server project.

Some notes about contributing patches are available at:

http://httpd.apache.org/dev/patches.html

For a substantial contribution we would need a signed Contributor 
License Agreement (CLA), see

http://www.apache.org/licenses/#clas

In order to document the availability of a patch and track its use, I 
suggest you open a bugzilla issue and attach the patch there:

https://issues.apache.org/bugzilla/

For a bigger patch you can also discuss the patch on this list before or 
after opening the bugzilla issue.

Regards,

Rainer