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 [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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
