Helo all, Massimiliano Pala wrote:
> Hi all, > > I have a question for you. Right now the OCSPD is a 'stand alone' application > that uses its own 'index.txt' ad DB backend. There is nothing wrong with > it, but It could be useful extending this daemon to directly be integrated > into OpenCA's DB backend. > > There are two ways: > > 1. Writing additional code into OCSPD package to support an external > tool that will look into the OpenCA DBMS and return the correct > status of the certificate to the daemon that will build the reply > accordingly; > > 2. Having OpenCA to write an additional index.txt when a certificate > status is modified and having the daemon to reload the index.txt > file when this occours. > I think that the best approach is the second one. And probably this will solve some problems regarding the sincronization of the imported-exported certificates (Michael, is it?). I also think that the index should be done in export-import.lib at export or import from RA. In this way we can have cosistent informations about certificates existent in RA and CA databases and their status. This can ease certificates sincronization between RA and CA. Regards, Alex > > Let me know what you think the best method could be... :-D > > -- > > C'you, > > Massimiliano Pala > > --o------------------------------------------------------------------------- > Massimiliano Pala [OpenCA Project Manager] [EMAIL PROTECTED] > [EMAIL PROTECTED] > http://www.openca.org Tel.: +39 (0)59 270 094 > http://openca.sourceforge.net Mobile: +39 (0)347 7222 365 ------------------------------------------------------- This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v? http://www.sun.com/javavote _______________________________________________ OpenCA-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-devel
