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?

In reply to Re^4: Open a file of a different user by JavaFan
in thread Open a file of a different user by Adler

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.