Hi Michael,

> there are several users which have trouble with common.conf and our
> linking. Should we introduce a common.conf in etc/ which has nothing to
> do with an interface? This file is only necessary for initServer. This
> would ease the packaging too.

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.

But that's just me, I have included the linking stuff into my own build
process now. :-)

Martin



-------------------------------------------------------
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

Reply via email to