On 07/09/2010 07:16 PM, Al Tobey wrote:
I've been working on setting up a puppet deployment using an external CA that signs certs for my puppet masters rather than using the internal self-signed certs. Along the way, I wanted to try having the certificate chain available on the agents so I added the "localcacertdir" option to puppet. localcacertdir points at a directory with all the required certs in it with the hash symlinks set up as openssl likes them (see openssl x509 -hash). I later found that this option is not necessary for normal operation once the CRL checks are relaxed a bit with the next patch, and am sending it here in case somebody else will find use for it.
What would this directory look like? I have a similar goal (external Certificate management) and I have not run across a standard layout. I am by no means an openssl expert though :)
The second patch relaxes the CRL checking flags sent to openssl so that verification can succeed even if all of the CRL's in the certificate chain are not available. With this option enabled (default is disabled to match current behavior), only the first certificate in the chain's CRL (the puppet master's CA cert) is verified. This makes my setup work well enough for me to move forward, although the correct solution is to distribute the entire CRL chain and have puppet use it. I'm still learning the internals of puppet and ruby at the same time so that will have to wait for another day.
What is the value of distributing the CRLs as opposed to the server doing it? Is this a performance thing?
-- bk -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
