From: Colin Walters <walters@verbum.org>
To: Thomas Bleher <bleher@informatik.uni-muenchen.de>
Cc: SELinux ML <selinux@tycho.nsa.gov>
Subject: Re: Access to xdm_t
Date: Wed, 29 Sep 2004 22:47:35 -0400 [thread overview]
Message-ID: <1096512456.5008.3.camel@nexus.verbum.private> (raw)
In-Reply-To: <20040929163222.GA4125@rom.cip.ifi.lmu.de>
On Wed, 2004-09-29 at 18:32 +0200, Thomas Bleher wrote:
> I have a question about access to xdm_t:
> With KDM 3.3 I am seeing a lot of accesses to xdm_t:fd and
> xdm_t:fifo_file from user processes (say user_lpr_t and user_gpg_t)
For Fedora we modified GDM to log the X session errors to
/tmp/xses-$USER.$RANDOM, you could probably do something similar with
KDM.
> Should these be allowed?
> If yes, should xdm_t get the attribute privfd?
I think it'd be better to move the X errors to /tmp. It's more
NFS-homedir friendly anyways.
--
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-09-30 3:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 16:32 Access to xdm_t Thomas Bleher
2004-09-29 17:50 ` Russell Coker
2004-09-29 22:01 ` Luke Kenneth Casson Leighton
2004-09-30 2:47 ` Colin Walters [this message]
2004-09-30 14:52 ` Thomas Bleher
2004-09-30 16:32 ` Colin Walters
2004-09-30 19:29 ` Luke Kenneth Casson Leighton
2004-09-30 20:41 ` Russell Coker
2004-10-01 0:47 ` Colin Walters
2004-10-01 9:35 ` Luke Kenneth Casson Leighton
2004-10-01 11:09 ` Russell Coker
2004-09-30 19:48 ` Russell Coker
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=1096512456.5008.3.camel@nexus.verbum.private \
--to=walters@verbum.org \
--cc=bleher@informatik.uni-muenchen.de \
--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.