Hi Eddy,
Sorry for being not clear enough in my original mail.
My fix adds support for CRL retrieval over HTTPS (and HTTP with
authentication). Such requirement is pretty common and, for example, is listed
in DoD PKI implementation guidelines.
Regards,
Alex
________________________________
From: Eddy Nigg (StartCom Ltd.) [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 28, 2007 16:13
To: OpenCA Developers
Cc: Alex Agranov
Subject: Re: [OpenCA-Devel] HTTPS support for OCSPD
Hi Alex,
I'm just thinking load....why should OCSP served over https? Isn't the response
signed anyway? I'm interested to know what lead you to add https, perhaps
something I didn't thought about....?
Alex Agranov wrote:
Hi,
I did a small change to the OCSPD v1.5.1rc1 source code that replaces built-in
HTTP protocol implementation by a cURL library. Major purpose for this change -
support of HTTPS protocol as well as authentication support for HTTP. I checked
the modified code in my environment and it seems to work nicely.
Would anybody be interested in this change?
Cheers,
Alex Agranov
Software Architect
AudioCodes Ltd.
--
Regards
Signer:
Eddy Nigg, StartCom Ltd.<http://www.startcom.org>
Jabber:
[EMAIL PROTECTED]<xmpp:[EMAIL PROTECTED]>
Blog:
Join the Revolution!<http://blog.startcom.org>
Phone:
+1.213.341.0390
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
OpenCA-Devel mailing list
OpenCA-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openca-devel
