lkml.org 
[lkml]   [2006]   [Aug]   [9]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateWed, 9 Aug 2006 00:01:06 -0400
From"Albert Cahalan" <>
SubjectRe: How to lock current->signal->tty
Stephen Smalley writes:

> SELinux is just revalidating access to the tty when the task
> changes contexts upon execve, and resetting the tty if the
> task is no longer allowed to use it.  Likewise with the open
> file descriptors that would be inherited.  No clearing of the
> ttys of other tasks required as far as SELinux is concerned,
> although that might not fit with normal semantics.

If the process goes back to the old context after a second
execve or via special rights, it ought regain access to the tty.

(just block access instead of resetting the tty)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-08-09 06:05    [from the cache]
©2003-2008