-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Guys, I looked at one of my puppet certs while troubleshooting a
problem getting Splunk to use them, and I discovered they look to be
1024 bits. Is there a way to change this to at the very least 2048 bits?
I prefer 3072 or 4096, but if it's not an
This probably isn't exactly what you're looking for, but that's covered at
http://reductivelabs.com/trac/puppet/wiki/MultipleCertificateAuthorities along
with other stuff to increase security. I haven't done it myself, but it would
be a bit of work.
-Patrick
On Feb 7, 2010, at 10:27 AM, Joe Mc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/02/10 5:27 AM, Joe McDonagh wrote:
> Hey Guys, I looked at one of my puppet certs while troubleshooting a
> problem getting Splunk to use them, and I discovered they look to be
> 1024 bits. Is there a way to change this to at the very least 2048 b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Turnbull wrote:
> On 8/02/10 5:27 AM, Joe McDonagh wrote:
>> Hey Guys, I looked at one of my puppet certs while troubleshooting a
>> problem getting Splunk to use them, and I discovered they look to be
>> 1024 bits. Is there a way to change this
Guys,
Sorry for the late response. I've spoken with Luke about talking at the
NYLUG meeting on the 17th, and going out for dinner/drinks afterwards. Luke
is on board, and the folks who run NYLUG are as well.
Currently we are working with IBM to reserve the meeting space for the
evening of the 17t
Hi
I am getting all these error from each client. This log is from one of
the puppet clients
http://pastebin.com/f141edbbc
I am guessing I need to replace the
/usr/share/puppet/rack/puppetmasterd/config.ru
(http://pastebin.com/f39e8e519)
with the ext/rack/files/config.ru of puppet 0.25.1
(http:
