Hi Sergei,I commited your patch for the OpenSSL prefix. I also retagged the CVS. I do not commit any OCSP related patches because I cannot test the OCSP stuff and I am a 100 percent beginner in case of OCSP. I think OCSP related patches should be commited by Max. If there are problems with the tagging then I can handle this.
BTW I think we will not rewrite all the C tools for OpenXPKI. So we need extra releases of all C programs. There are two possibilities - OpenXPKI releases such packages by itself or OpenCA does it. I don't like the idea that OpenXPKI releases OpenCA stuff (only with another branding). Therefore I would prefer extra releases of the C tools but this would require that we move the C tools to seperate CVS areas or the management is really difficult.
So Max should make a decision what he wants. I would prefer seperate (or better updated) CVS areas for openca-scep, openca-sv and openca-oscp. I can make the transition (including branch management) but it is Max decision what to do. Only migrating the source to OpenXPKI to have control over the releases is the absolute worst case which come to my mind because the home of the source code is OpenCA.
Best regards Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
smime.p7s
Description: S/MIME Cryptographic Signature
