in reply to Re^2: Open a file of a different user
in thread Open a file of a different user

Javafan, please note that from a security standpoint:
The individual home directories should not have world read write access, this is what group permissions and directories are for.
If the user needs access to a file that is owned by another user, it should be stored in a common access area. In fact, there are some security related functions (of which SSH is one) that refuse to run if the user's home directory is world readable.
File access controls are nice (and selinux context controls even nicer), but group read/write access (anything with more than one user) needs appropriate permissions set and enforced.

Replies are listed 'Best First'.
Re^4: Open a file of a different user
by JavaFan (Canon) on May 13, 2010 at 13:04 UTC
    If the user needs access to a file that is owned by another user, it should be stored in a common access area.
    Define "common access". Execute permission on the directory is enough, because all that's needed in finding the inode number given the file name: 
    $ id -u
1500
$ id -g
1000
$ ls -ld Foo
drwx--x--x  2 root root 4096 May 13 08:54 Foo
$ cat Foo/bar
Hello, world!
$ sudo ls -l Foo
total 4
-rw-r--r--  1 root root 13 May 13 08:55 bar
$

    [download]
    In fact, there are some security related functions (of which SSH is one) that refuse to run if the user's home directory is world readable.
    Yes, and penguins are black and white. How does that relate to using file ACLs?
[reply]
[d/l]

In Section Seekers of Perl Wisdom