From: Russell Coker <rcoker@redhat.com>
To: Colin Walters <walters@redhat.com>
Cc: dwalsh@redhat.com, selinux@tycho.nsa.gov
Subject: Re: [patch] fix /var/run/console bits
Date: Wed, 4 Aug 2004 20:07:03 +1000 [thread overview]
Message-ID: <200408042007.03512.rcoker@redhat.com> (raw)
In-Reply-To: <1091584911.8312.7.camel@nexus.verbum.private>
On Wed, 4 Aug 2004 12:01, Colin Walters <walters@redhat.com> wrote:
> Currently /var/run/console is labeled as xdm_var_run_t, which is totally
> wrong, since it's actually owned by pam_console. I noticed this while I
> was trying to work on the D-BUS policy, which recently gained console
> user authentication.
>
> Attached is a patch which creates a new type for it, grants the
> requisite permissions to login and xdm. I still think we need a nicer
> way of mapping the PAM permissions in policy. The only reason that
> login and xdm are granted these permissions is because they happen to
> ship with pam_console in their PAM stack on Fedora, presumably. (IIRC
> Debian doesn't use pam_console).
I think that perhaps the following would be good for the fc entry to keep the
convention:
/var/run/console/(.*)? system_u:object_r:pam_var_console_t
This is not what we want. Ideally we will never have any files of type
var_run_t.
rw_dir_create_file(xdm_t, var_run_t)
rw_dir_create_file($1_login_t, var_run_t)
I guess that the following code is to allow the xdm to check which login
processes are active when searching for an unused virtual console. If my
guess is correct then signull access would need to be granted to getty_t and
userdomain. Of course if you hard-code a VC in the config file then maybe
this isn't needed.
# FIXME: what is this for?
ifdef(`xdm.te', `
allow xdm_t $1_login_t:process { signull };
')
--
http://apac.redhat.com/disclaimer
See above URL for disclaimer.
--
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 prev parent reply other threads:[~2004-08-04 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 2:01 [patch] fix /var/run/console bits Colin Walters
2004-08-04 9:30 ` Luke Kenneth Casson Leighton
2004-08-04 10:07 ` Russell Coker [this message]
2004-08-04 13:03 ` Colin Walters
2004-08-04 13:19 ` Daniel J Walsh
2004-08-05 7:40 ` Russell Coker
2004-08-05 19:23 ` Stephen Smalley
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=200408042007.03512.rcoker@redhat.com \
--to=rcoker@redhat.com \
--cc=dwalsh@redhat.com \
--cc=selinux@tycho.nsa.gov \
--cc=walters@redhat.com \
/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.