On Tue, Sep 13, 2005 at 10:01:58AM -0700, Linus Torvalds wrote:
>
>
> On Tue, 13 Sep 2005, Al Viro wrote:
> >
> > What we need is to decide what kind of access control do we really want on
> > /proc/<pid>/task. That's it.
>
> I don't think any controls at all. The real control should then be on the
> /proc/<pid>/task/<tid> access, which should be the same as the /proc/<pid>
> controls (except for thread <tid> rather than thread <pid>, of course)
Well... If exposing the list of tasks in a group is OK, we can just leave
->permission NULL for that sucker. If it's not (and arguably it can be
sensitive information), we have a bigger problem - right now chroot boundary
is the only control we have there; normally anyone can ls /proc/<whatever>/task
and see other threads.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |