Jira (PUP-6359) Completely remove allow/deny rules from fileserver.conf syntax

[Jeremy Barlow (JIRA)]

Title: Message Title

Jeremy Barlow commented on PUP-6359   Re: Completely remove allow/deny rules from fileserver.conf syntax So it might be better to only fail the request if there is a deny directive or an allow directive for something other than *. Josh Cooper, that sounds reasonable to me. What do you think we should do in the case where an auth rule doesn't have any allow or deny directives. For example, let's say the fileserver.conf file had this: [pe_packages] path /opt/puppetlabs/server/data/packages/public [pe_modules] path /opt/puppetlabs/server/share/installer/modules Today, any request to access either of the mount points would be denied. For Puppet 5, would you think the behavior should implicitly change to act like allow * instead? Assuming we're eventually intending to eliminate all use of the auth directives from the fileserver.conf file, I think this would make sense – although it could arguably be construed as a security issue if access to some mount points that had not previously been denied by auth.conf rules at a higher level started to be granted to all users after upgrading to Puppet 5. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.