Closed (fixed)
Project:
Provision
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Jan 2012 at 04:56 UTC
Updated:
12 Jun 2014 at 08:41 UTC
Jump to comment: Most recent
In line 233 of provision.config.inc, we set the drushrc file to chmod 0400. This prevents shell users who belong to the 'aegir' group from running some drush commands against sites from the CLI, as they can't open the drushrc.php file to load various attributes.
Can we afford to set this file to chmod 0440 and just ensure the 'group' is also 'aegir'? Do you foresee any major security issues with this? I can't, but I wanted to get some insight from anarcat or others.
Comments
Comment #1
chrisschaub commentedThey should be 0440 so sites can use acl to get drush working. The provision_acl module sets the group acl correctly for the client, but without the group bit set to read, it doesn't work. I don't see any security issues since the perms are aegir:aegir anyway. So, I second this change!
Comment #2
anarcat commentedGo.
I fail to see how this would keep the provision_acl module from working though. But anyways, let's do it.
Comment #3
chrisschaub commentedGreat. What happens is that the acl permissions set the group bit via provision_acl. But, the file has no group read bit set. So, acl can't give you permissions that don't exist on the filesystem -- it can just add users to use the existing permissions. So, drushrc.php can't be read by drush or a client user via shell in a site directory. Changing to 0440 works well.
Thanks!
Comment #4
Anonymous (not verified) commentedFix committed.