On Jan 3, 2013, at 2:02 PM, Forrie wrote:
> I see the ChangeLog in 3.0.2 and this bug is still not addressed? Is there
> a technical problem that is not yet resolved, or is this just a matter of
> priority and time.
Forrie this is on the table for 3.1 which will have a Release Candidate bui
Jeff,
Thanks for the reply. This is the first Puppet distribution that I've
upgraded to that required a lot of manual changes. But that comes with the
territory :-)
What I think would be very useful is to not only include sample *.conf
files, init scripts, and such, but also example usage o
On Tue, Oct 2, 2012 at 11:09 AM, Forrie wrote:
> The ChangeLog and the PR are not clear about this. In fact, the
> documentation is vague and doesn't really mention allow_ip at all. This
> should be updated and made more clear?
Forrie,
I agree this wasn't very clear. I too had a hard time fi
Check out the example auth.conf that comes with the distribution, it's
heavily commented and should point the way:
https://github.com/puppetlabs/puppet/blob/master/conf/auth.conf
On Tuesday, October 2, 2012 11:09:08 AM UTC-7, Forrie wrote:
>
> The ChangeLog and the PR are not clear about this.
The ChangeLog and the PR are not clear about this. In fact, the
documentation is vague and doesn't really mention allow_ip at all. This
should be updated and made more clear?
I will give this a try later on, on a test system, and see if that solves
the problem.
Thanks.
On Tuesday, Octobe
Oh, sorry, you mention that you already found that changelog entry. I
misread that part.
On Mon, Oct 1, 2012 at 10:27 PM, Matthaus Owens wrote:
> In Puppet 3.x, allow directives are limited to hostnames, if you wish
> to allow an ip address, the allow_ip directive should be used. This
> was in re
In Puppet 3.x, allow directives are limited to hostnames, if you wish
to allow an ip address, the allow_ip directive should be used. This
was in response to CVE-2012-3408
(http://puppetlabs.com/security/cve/cve-2012-3408/).
On Mon, Oct 1, 2012 at 5:48 PM, Forrie wrote:
> I've seen mention of this
I've seen mention of this error in several places, with different causes.
So before I posted here, I attempted to resolve this on my own.
I corrected the change from puppet:///files to puppet:/// in my manifests
*.pp files.
No changes were made to the auth.conf file, and I did note in the Ch