Linux permissions: Difference between revisions

From Bitpost wiki
No edit summary
No edit summary
Line 5: Line 5:


If you need to share an existing folder, you need to do g+w and also retroactively update g+s on all the directories manually with this stupid hack (becuase -R doesn't work, stupid linux bullshit):
If you need to share an existing folder, you need to do g+w and also retroactively update g+s on all the directories manually with this stupid hack (becuase -R doesn't work, stupid linux bullshit):
  sudo chmod -R g+w myshare
  chmod g+ws existingshare
  find myshare -type d -exec chmod g+s '{}' \;
find existingshare -type d -exec chmod g+ws {} \;
  find existingshare -type f -exec chmod g+w {} \;


=== Restricting a user to a specific folder ===
=== Restricting a user to a specific folder ===

Revision as of 18:45, 23 June 2022

Managing a shared folder with a linux group

sudo groupadd mygroup # create a group
sudo usermod -a -G mygroup myuser # add yourself (and others)
mkdir myshare && chmod g+ws myshare # set up a folder for sharing - you want g+w and g+s

If you need to share an existing folder, you need to do g+w and also retroactively update g+s on all the directories manually with this stupid hack (becuase -R doesn't work, stupid linux bullshit):

chmod g+ws existingshare
find existingshare -type d -exec chmod g+ws {} \;
find existingshare -type f -exec chmod g+w {} \;

Restricting a user to a specific folder

I have found that for several folders on my server I do not have the w+x bit set for folders:

drwxrwxr-- 12 m m 4.0K Feb  3  2017 .

This was killing me, as I tried to set user-specific permissions on symlinks to subfolders deep within the top level folder. They would fail because the user could not cd to the folder due to the missing +x. You have to make sure the WHOLE F'IN FOLDER CHAIN HAS g+x ON IT in order for a specific user to be able to cd to it.