Michael Bell wrote:
Michael Portz wrote:
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
Well...fixing the mis-placements by hand made my PKI work for now :)
Thanks!
Btw: @enroll_ca_certificate_states@ was only an example. Aparently
configure_etc.sh did not one single "@..@" replacement in the server
directory.
I at least tried to configure my server so I can start from a thoroughly
wiped installation (btw: its Fedora 1) each time i fixed a problem. So I
dont think its a problem of ancient versions lurking in the shadows... :)
Regards
Michael
--
accom GmbH & Co. KG
Gruener Weg 100
52070 Aachen
Tel: +49 241 918 5228
Fax: +49 241 918 5299
-------------------------------------------------------
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
