On Nov 10, 2010, at 4:29 AM, Chris wrote:
> How are other people getting around this? Do you just allow all
> clients to access all keys? Is there a native type, or an auth.conf
> trick, that I'm missing? Or a more binary-friendly encoding than JSON/
> PSON ?
I send a different message with a r
> All good, except that in 0.25 and up (which we're slowly migrating
> to), this often doesn't work. The rest APIs require UTF-8 content, and
> keys are binary, so catalog requests fail if the key happens to
> contain bytes which aren't valid UTF-8. (http://
> projects.puppetlabs.com/issues/4832 ta
Hi Chris,
2010/11/10 Chris
> [...]
> file{"/path/to/foo.key": source=>"puppet:///keys/foo.key"} , because
> any valid puppet client could access foo.key.
> [...]
>
you are not sticked to the puppet file server, you can also use something
like this:
file {
"/path/to/file":
source => "/
Hi all,
Hi all,
We use puppet for, amongst other things, managing the private-key
files needed for things like SSL certificates for HTTPS web servers.
We have a few constraints on how these are handled, and changes in
recent versions of puppet are making this harder than it perhaps ought
to be to
