Dr. Rodney McDuff wrote:
I've been trying to run multiple independent OCSP Responders on same box and running into trouble concerning the locking of the semaphore (or lock file). The code as if stands uses the same semaphore key (or lock file) for each independent server. The patch below is an attempt to fix the problem by linking the semaphore key to the process ID (or using mkstemp to create a random lock file).
Why did you do it ? You know that OCSP can respond for different CAs, right?
Or did you needed different signing keypairs for each configured CA ?
--
Best Regards,
Massimiliano Pala
--o------------------------------------------------------------------------
Massimiliano Pala [OpenCA Project Manager] [EMAIL PROTECTED]
Tel.: +39 (0)11 564 7081
http://security.polito.it Fax: +39 178 270 2077
Mobile: +39 (0)347 7222 365
Politecnico di Torino (EuroPKI)
Certification Authority Informations:
Authority Access Point http://ca.polito.it
Authority's Certificate: http://ca.polito.it/ca_cert/en_index.html
Certificate Revocation List: http://ca.polito.it/crl02/crl.crl
--o------------------------------------------------------------------------
smime.p7s
Description: S/MIME Cryptographic Signature
