Hi Martin,
Martin Bartosch wrote:
I don't think it is useful to introduce another config file if it is not really needed. Keeping the config files in sync as the software improves is not very easy, because if the default layout of cert profiles is changed you have to port your changes to the new config files when "fresh" releases appear. Per-Request-type and per-node changes gives a lot of places to change (and to make mistakes).
Perhaps the linking heuristics should be improved - I am not sure, but I think the best way would not to be to link to the first conf file found in the servers directory, but always to node.conf. This should be the most generic file and should always be present.
The problem is that node.conf is sometimes not installed at the target system. So what about adding a new target to etc/Makefile which installs node.conf to common.conf and does not only link common.conf. I think this is perhaps the most safe way. BTW this would reduce the trouble with linking.
Comments?
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 _______________________________________________________________
------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Openca-Users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/openca-users
