Richard Weinberger <[email protected]> writes: > On Sun, Jul 20, 2014 at 12:55 PM, Andreas Schwab <[email protected]> > wrote: >> Joakim Tjernlund <[email protected]> writes: >> >>> Andreas Schwab <[email protected]> wrote on 2014/07/19 22:21:59: >>>> >>>> Joakim Tjernlund <[email protected]> writes: >>>> >>>> > Trying to real /proc/<pid>/exe I noticed I could not read links not >>>> > belonging to my user such as: >>>> > jocke > ls -l /proc/1/exe >>>> > ls: cannot read symbolic link /proc/1/exe: Permission >>> denied >>>> > >>>> > Is this expected? >>>> >>>> Yes. This information is considered private. >>> >>> I don't understand why though. >> >> It would allow bypassing access restrictions. > > Do you have an example?
proc symlinks are special because they actually resolve to the inode. Andreas. -- Andreas Schwab, [email protected] GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
