Re: ls -l /proc/1/exe -> Permission denied

2014-07-21 Thread Eric W. Biederman
Richard Weinberger writes: > Am 20.07.2014 13:51, schrieb Andreas Schwab: >> Richard Weinberger writes: >>> Do you have an example? >> >> proc symlinks are special because they actually resolve to the inode. > > Ah. If an attacker manages the kernel to follow the symlink he could > indirectly a

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Joakim Tjernlund
Richard Weinberger wrote on 2014/07/20 22:00:02: > > Am 20.07.2014 21:15, schrieb Joakim Tjernlund: > > Richard Weinberger wrote on 2014/07/20 14:05:41: > >> > >> Am 20.07.2014 13:51, schrieb Andreas Schwab: > >>> Richard Weinberger writes: > Do you have an example? > >>> > >>> proc symlin

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Richard Weinberger
Am 20.07.2014 21:15, schrieb Joakim Tjernlund: > Richard Weinberger wrote on 2014/07/20 14:05:41: >> >> Am 20.07.2014 13:51, schrieb Andreas Schwab: >>> Richard Weinberger writes: Do you have an example? >>> >>> proc symlinks are special because they actually resolve to the inode. >> >> Ah.

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Joakim Tjernlund
Richard Weinberger wrote on 2014/07/20 14:05:41: > > Am 20.07.2014 13:51, schrieb Andreas Schwab: > > Richard Weinberger writes: > >> Do you have an example? > > > > proc symlinks are special because they actually resolve to the inode. > > Ah. If an attacker manages the kernel to follow the sy

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Richard Weinberger
Am 20.07.2014 13:51, schrieb Andreas Schwab: > Richard Weinberger writes: >> Do you have an example? > > proc symlinks are special because they actually resolve to the inode. Ah. If an attacker manages the kernel to follow the symlink he could indirectly access that file. Thanks for pointing thi

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Richard Weinberger
Am 20.07.2014 13:51, schrieb Andreas Schwab: > Richard Weinberger writes: >> Do you have an example? > > proc symlinks are special because they actually resolve to the inode. Ah. If an attacker manages the kernel to follow the symlink he could indirectly access that file. Thanks for pointing thi

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Richard Weinberger
Am 20.07.2014 13:51, schrieb Andreas Schwab: > Richard Weinberger writes: >> Do you have an example? > > proc symlinks are special because they actually resolve to the inode. Ah. If an attacker manages the kernel to follow the symlink he could indirectly access that file. Thanks for pointing thi

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Andreas Schwab
Richard Weinberger writes: > On Sun, Jul 20, 2014 at 12:55 PM, Andreas Schwab > wrote: >> Joakim Tjernlund writes: >> >>> Andreas Schwab wrote on 2014/07/19 22:21:59: Joakim Tjernlund writes: > Trying to real /proc//exe I noticed I could not read links not > belongin

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Joakim Tjernlund
Richard Weinberger wrote on 2014/07/20 13:06:30: > > On Sun, Jul 20, 2014 at 12:55 PM, Andreas Schwab wrote: > > Joakim Tjernlund writes: > > > >> Andreas Schwab wrote on 2014/07/19 22:21:59: > >>> > >>> Joakim Tjernlund writes: > >>> > >>> > Trying to real /proc//exe I noticed I could not

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Richard Weinberger
On Sun, Jul 20, 2014 at 12:55 PM, Andreas Schwab wrote: > Joakim Tjernlund writes: > >> Andreas Schwab wrote on 2014/07/19 22:21:59: >>> >>> Joakim Tjernlund writes: >>> >>> > Trying to real /proc//exe I noticed I could not read links not >>> > belonging to my user such as: >>> > jocke > ls -l

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Andreas Schwab
Joakim Tjernlund writes: > Andreas Schwab wrote on 2014/07/19 22:21:59: >> >> Joakim Tjernlund writes: >> >> > Trying to real /proc//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 /pr

Re: ls -l /proc/1/exe -> Permission denied

2014-07-20 Thread Joakim Tjernlund
Andreas Schwab wrote on 2014/07/19 22:21:59: > > Joakim Tjernlund writes: > > > Trying to real /proc//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 > > > >

Re: ls -l /proc/1/exe -> Permission denied

2014-07-19 Thread Andreas Schwab
Joakim Tjernlund writes: > Trying to real /proc//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.

Re: ls -l /proc/1/exe -> Permission denied

2014-07-19 Thread Richard Weinberger
Am 18.07.2014 17:05, schrieb Joakim Tjernlund: > Joakim Tjernlund/Transmode wrote on 2014/07/18 15:49:17: >> >> Richard Weinberger wrote on 2014/07/18 > 14:58:30: >>> >>> On Thu, Jul 17, 2014 at 1:18 PM, Joakim Tjernlund >>> wrote: Trying to real /proc//exe I noticed I could not read link

Re: ls -l /proc/1/exe -> Permission denied

2014-07-18 Thread Joakim Tjernlund
Joakim Tjernlund/Transmode wrote on 2014/07/18 15:49:17: > > Richard Weinberger wrote on 2014/07/18 14:58:30: > > > > On Thu, Jul 17, 2014 at 1:18 PM, Joakim Tjernlund > > wrote: > > > Trying to real /proc//exe I noticed I could not read links not > > > belonging to my user such as: > > > jock

Re: ls -l /proc/1/exe -> Permission denied

2014-07-18 Thread Joakim Tjernlund
Richard Weinberger wrote on 2014/07/18 14:58:30: > > On Thu, Jul 17, 2014 at 1:18 PM, Joakim Tjernlund > wrote: > > Trying to real /proc//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 /pro

Re: ls -l /proc/1/exe -> Permission denied

2014-07-18 Thread Richard Weinberger
On Thu, Jul 17, 2014 at 1:18 PM, Joakim Tjernlund wrote: > Trying to real /proc//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? Why do you think

ls -l /proc/1/exe -> Permission denied

2014-07-17 Thread Joakim Tjernlund
Trying to real /proc//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? uname -a Linux gentoo-jocke 3.12.21 -- To unsubscribe from this list: send the line