All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: kdm 3.3 is deleting and recreating /var/run/xdmctl
Date: Sun, 15 Aug 2004 19:40:04 +0100	[thread overview]
Message-ID: <20040815184004.GL11256@lkcl.net> (raw)

heads up for something to watch out for: kdm 3.3 is deleting and
then recreating /var/run/xdmctl, presumably as a way of clearing
out any messy sockets in that directory.

kdm 3.2.2 did not behave in this manner.

it means that people doing a new install of kdm under selinux
may run into problems.

e.g. if dpkg has not been given write permission to /var/run
in order for /var/run/xdmctl to be created at postinst time.

e.g. if postinst does _not_ create this directory, it doesn't exist,
and kdm attempts to create it for the first time.

i am not allowing the xdm_t permission to unlink and create in
var_run_t: consequently, if that directory already exists, everything
is hunky-dory: selinux bans kdm from deleting it, and consequently,
it still exists such that kdm doesn't try to create it.

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.

                 reply	other threads:[~2004-08-15 18:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040815184004.GL11256@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.