From: Daniel J Walsh <dwalsh@redhat.com>
To: SELinux <SELinux@tycho.nsa.gov>
Subject: Problems with /dev/tty on reboot.
Date: Wed, 26 Nov 2003 08:48:27 -0500 [thread overview]
Message-ID: <3FC4AF2B.3060301@redhat.com> (raw)
How should we handle the situation where contexts end up in the wrong
contexts because of crashes or reboots.
Currently if you login to a box as user_t, and then the system crashes
or you reboot the /dev/tty has the wrong context on it, so if the next
user that attempts to login has staff_t he will not be able to gain
access to the device. I have put a
setfiles file_context /dev/tty in my rc scripts as a stop gap, but that
is not a clean solution. Also this can probably happen to other files
that have their contexts changed by running processes. Ideas on how to
solve this problem??
Dan
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next reply other threads:[~2003-11-26 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 13:48 Daniel J Walsh [this message]
2003-11-26 14:14 ` Problems with /dev/tty on reboot Stephen Smalley
2003-11-26 14:50 ` Daniel J Walsh
2003-11-26 15:33 ` Stephen Smalley
2003-11-26 16:26 ` Daniel J Walsh
2003-11-26 16:33 ` Tom
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=3FC4AF2B.3060301@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.