From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: kde 3.3's kdm creating /var/run/xdmctl
Date: Mon, 23 Aug 2004 21:54:04 +0100 [thread overview]
Message-ID: <20040823205404.GC7540@lkcl.net> (raw)
this is a bit of an issue.
if /var/run/xdmctl gets accidentally deleted, kde sessions will not be
able to do a shutdown or restart from the logout menu.
the reason is because xdm_t doesn't have permission to recreate
the /var/run/xdmctl directory.
the suggestion of doing touch /var/run/xdmctl/.keep will simply
stop kdm from rm'ing /var/run/xdmctl, but if the directory
ever happens to _successfully_ be deleted (permissive mode
for example) ...
also i find that on creation of this directory, its permission
is set to var_run_t not xdm_var_run_t.
i'm not entirely sure what to do.
at the moment as a preliminary measure i've added permissions
for xdm_t to create, access and delete sockets in both var_run_t
_and_ xdm_var_run_t in order to deal with the mess.
help?
l.
--
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love. If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net"> lkcl.net </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
--
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:[~2004-08-23 20:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 20:54 Luke Kenneth Casson Leighton [this message]
2004-08-24 11:02 ` kde 3.3's kdm creating /var/run/xdmctl Stephen Smalley
2004-08-24 22:33 ` Luke Kenneth Casson Leighton
2004-08-28 16:22 ` Luke Kenneth Casson Leighton
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=20040823205404.GC7540@lkcl.net \
--to=lkcl@lkcl.net \
--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.