Hi Michael,
I took the configuration section "1. the node acts as CA only". I left everything unchanged, so the first entry remained:
<option> <name>enroll_ca_certificate_states</name> <value>VALID</value> </option>
First the fast solution is to replace @enroll_ca_certificate_states@ in node.conf and ca.conf by VALID. Second the slower solution is to search for the mistake. Some time ago we had a typo in config.xml which creates exact this problem. If you have no fully new installation then your configuration files are perhaps from the old installation and this can cause old problems - like a typo.
Michael -- ------------------------------------------------------------------- Michael Bell Email: [EMAIL PROTECTED] ZE Computer- und Medienservice Tel.: +49 (0)30-2093 2482 (Computing Centre) Fax: +49 (0)30-2093 2704 Humboldt-University of Berlin Unter den Linden 6 10099 Berlin Email (private): [EMAIL PROTECTED] Germany http://www.openca.org
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Openca-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-users
