Hello Wytze, It is definitely a bug.. the 1.9.0 version is not really production ready.. I am finishing some details for the new version of LibPKI which is required for the OCSPD v2.0 which will support the usage of different tokens to sign responses.
A solution to your problem would be to have the same key certified by different CAs and include all the server's certificates in the other certs.. I am not sure if the clients will be able to use the right certificates, but it might work.. Cheers, Max P.S.: The new release of the OCSPD has been pushed back because of lack of time and resources.. I hope to have it out soon, though. On 06/11/2010 10:18 AM, Wytze van der Raay wrote:
I am having a problem with running ocspd 1.9.0 with multiple CA's.
[...]
It used to work with the older 1.5.2 version of ocspd, but that one has serious coding problems in the threading logic, so I cannot use it :-(
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________ Openca-Users mailing list Openca-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openca-users
