New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New security setting in BOA Aegir 2.2.1 : Permission denied for /bin paths #296
Comments
|
There is a parameter in that forces strict permissions on /usr/bin .. it You need to add this particular user to the group 'users' to sort it out. On 3 April 2014 00:17, David Hunt notifications@github.com wrote:
|
|
Correct, it is by design. If you want to whitelist any non-BOA users, add them to the "users" group:
|
|
Heh. Was just writing that, thanks chuze and omega8cc. Is this a new security setting for this version of Aegir? Did I miss it in the release notes? |
|
Yeah, we should document this better: https://github.com/omega8cc/boa/blob/master/CHANGELOG.txt#L454 |
|
We have added it to docs, but we should explain this also in the release notes. https://github.com/omega8cc/boa/blob/master/docs/SECURITY.txt |
|
Ok, good to know. Thanks for the help all. |
dnotes commentedApr 2, 2014
I'm getting a bunch of permission denied errors on commands like "ls" for the main system user (ubuntu@ or vagrant@) after up-stable to 2.2.1. This is happening both on my local Vagrant box and on a cloud server. The octopus users seem to be unaffected, and sudo still works fine and gives access to the entire system. Have you seen this before or do you know what may be happening? Looks to me like the permissions for /bin were removed from that user, if that is even possible.
Edit: text of the messages, so that the next person can find this:
The text was updated successfully, but these errors were encountered: