Matthaus Owens <matth...@puppetlabs.com> writes: > 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/).
Thank you for your help. Looks like something is still broken. I replaced all "allow" directoves in fileserver.conf with allow_ip; I still had the same errors: ### Broken! [files] path /etc/puppet/files allow_ip 129.102.0.0/16 allow_ip 2001:660:3004::/49 [private] path /etc/puppet/files-private/%H allow_ip 129.102.0.0/16 allow_ip 2001:660:3004::/49 # EOF I then replaced them with "allow *", which fixed the problem but introduces a change of behavior: ### Working [files] path /etc/puppet/files allow * [private] path /etc/puppet/files-private/%H allow * # EOF This is definitely a regression. -- A -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
