From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@epoch.ncsc.mil>, SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: kde 3.3's kdm creating /var/run/xdmctl
Date: Sat, 28 Aug 2004 17:22:35 +0100 [thread overview]
Message-ID: <20040828162235.GA9796@lkcl.net> (raw)
In-Reply-To: <20040824223313.GF12140@lkcl.net>
On Tue, Aug 24, 2004 at 11:33:13PM +0100, Luke Kenneth Casson Leighton wrote:
> On Tue, Aug 24, 2004 at 07:02:09AM -0400, Stephen Smalley wrote:
> > On Mon, 2004-08-23 at 16:54, Luke Kenneth Casson Leighton wrote:
> > > 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.
> >
> > What creates the directory?
>
> i believe it's kdm.
>
> > If it is kdm itself, then extend the
> > file_type_auto_trans(xdm_t, var_run_t, xdm_var_run_t, fifo_file) rule to
> > also cover dir (replace fifo_file with { dir fifo_file}).
>
> okay, great, i'll try that out.
seems to have worked. unlink permission isn't granted but the
directory /var/run/xdmctl is deleted on logout only to be recreated
at login anyway.
thanks stephen.
l.
--
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.
prev parent reply other threads:[~2004-08-28 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 20:54 kde 3.3's kdm creating /var/run/xdmctl Luke Kenneth Casson Leighton
2004-08-24 11:02 ` Stephen Smalley
2004-08-24 22:33 ` Luke Kenneth Casson Leighton
2004-08-28 16:22 ` Luke Kenneth Casson Leighton [this message]
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=20040828162235.GA9796@lkcl.net \
--to=lkcl@lkcl.net \
--cc=sds@epoch.ncsc.mil \
--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.