On 2024-01-22 09:48, -pj via openSUSE Users wrote:
On 01-22-2024 02:23AM, Carlos E. R. wrote:
On 2024-01-22 09:03, -pj via openSUSE Users wrote:
Hello there, What I ended up doing (perhaps to soon) was the following:
chgrp paul -R /home/paul
-------------------------------------------------------------------------------------------------------
paul@paul-Thinkcentre-M57p:/home> pwd /home -----------------------------------------------------------------------------------------------------
paul@paul-Thinkcentre-M57p:/home> ls -lah total 0 dr-xr-xr-x 1 root root 14 Jan 21 18:18 .drwxr-xr-x 1 root root 142 Jun 3 2021 ..drwx------ 1 deb deb 318 Jan 22 00:02 debdrwx------ 1 paul paul 878 Jan 22 00:47 paulpaul@paul-Thinkcentre-M57p:/home> cd paul paul@paul-Thinkcentre-M57p:~> ls -lah total 108K drwx------ 1 paul paul 878 Jan 22 00:47 .dr-xr-xr-x 1 root root 14 Jan 21 18:18 ..-rw------- 1 paul paul 0 Jan 10 22:04 1-10-24-test-0.txt -rw------- 1 paul paul 0 Jan 10 22:06 1-10-24-test-1.txt -rw------- 1 paul paul
Wrapping is destroyed when replying.
I think "chgrp paul -R /home/paul" was correct. What problem did you see?
I was pleased at the outcome but I believe I maybe should not have "chmod -R go-rwx" perhaps instead chmod -R o-rwx but if /home has paul drwx------ 1 paul paul 878 Jan 22 00:47 paul. I could have left the insides of /home/paul as they were while retaining security I think maybe?Following man chgrp man page 1 was not helpful for me, I was trying to pass: 'chgrp -R paul users'while located in /home directory (did not function).
If you use group "paul", the rationale is that users in that group can at least read the files. It is up to you to create users in that group or not. If you do not want the to give access even to group paul, you could as well have left the group as "users" and deny access to them.
------------------------------------------------------------------------------------------------- paul@paul-Thinkcentre-M57p:~>
Thinkcentre-M57p:~> groups paul paul : paul audio cdrom
------------------------------------------------------------ Thinkcentre-M57p:~> id -a uid=1000(paul) gid=100 groups=100,488(cdrom)
cat /etc/passwd paul:x:1000:1000:Paul:/home/paul:/bin/bash ------------------------------------------------------------------------------------------------------------
I passed as superuser: chmod -R go-rwx at /home/paul then chmod -R go-rwx inside /home/paul after changing groups.
Why, what's the intention?
When I have done something like that, there is a way to differentiate directories from files. Files do not need 'x', directories do.
Thank for telling me of this about files do not need "x" execute permissions and directories do. Are scripts the same way as files then?
script files do need the x, if you want users in the group paul to be able to execute them. In that case you need to script something, to find all files or directories that are executable by the user, then give execute permission to the group as well.
Was this a mistake to have done this, following the chgrp -R paul /home/paul ? I can significantly attempt to affirm that user paul was the first user to be added during installation of the openSUSE Tumbleweed on the machine (install was maybe 2 years ago on this particular machine). I honestly do not know why each user after the supposed first user added to the OS *has* to become a member of the users group.
That's *SUSE policy for decades, yes.
I see more now thanks for verify on this policy.
I have never bothered much to find out a way to change the policy locally.
Can't any user just open another user files then by default? What do people typically do concerning this scenerio?
The rationale is that a computer is used by a family or group of friends or coworkers, all of which may need to read each other files. If that is not desired, each user can simply remove the group permissions. Other distributions may do differently. It would be nice to be able to choose. There are pro and cons for each method. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.5 (Laicolasse))