From: "Albert Cahalan" <acahalan@gmail.com>
To: sds@tycho.nsa.gov, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org, davem@redhat.com,
viro@ftp.linux.org.uk
Subject: Re: How to lock current->signal->tty
Date: Wed, 9 Aug 2006 00:01:06 -0400 [thread overview]
Message-ID: <787b0d920608082101h2f1c1200rf94be91eefdcdac0@mail.gmail.com> (raw)
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)
next reply other threads:[~2006-08-09 4:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 4:01 Albert Cahalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-08 15:17 Alan Cox
2006-08-08 15:10 ` Arjan van de Ven
2006-08-08 15:44 ` Alan Cox
2006-08-08 16:41 ` Luck, Tony
2006-08-08 17:50 ` Alan Cox
2006-08-09 8:09 ` Jes Sorensen
2006-08-09 10:44 ` Alan Cox
2006-08-09 11:26 ` Jes Sorensen
2006-08-09 16:24 ` Luck, Tony
2006-08-09 18:10 ` Jes Sorensen
2006-08-08 22:06 ` Jan Kara
2006-08-08 17:11 ` Stephen Smalley
2006-08-08 17:43 ` Alan Cox
2006-08-08 17:44 ` Stephen Smalley
2006-08-08 18:10 ` Alan Cox
2006-08-08 20:02 ` Stephen Smalley
2006-08-13 21:34 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=787b0d920608082101h2f1c1200rf94be91eefdcdac0@mail.gmail.com \
--to=acahalan@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®