lkml.org 
[lkml]   [1999]   [Jul]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
DateTue, 20 Jul 1999 14:30:27 +0100 (GMT)
FromChris Evans <>
SubjectRe: [RFC] new kernel syscall

On Mon, 19 Jul 1999, Oliver Xymoron wrote:

> > because a daemon running as e.g. "gdm" can clear current->dumpable and
> > then a breach of a different "gdm" sibling process finds itself unable to
> > attach to its sibling and snoop passwords.
>
> As long as privileged users can still get around it. It would be annoying

Of course. The call would tap into the existing mechanism of
current->dumpable. And current CAP_PTRACE allows to trace any process
(except init!) regardless of dumpable, uid, gid, capabilities etc.

Chris


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:53    [from the cache]
©2003-2010