All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	Karl MacMillan <kmacmillan@tresys.com>,
	SELinux@tycho.nsa.gov, dwalsh@redhat.com
Subject: Re: file_type_auto_trans is not sufficient
Date: Tue, 31 May 2005 22:10:27 +0100	[thread overview]
Message-ID: <20050531211027.GD11815@lkcl.net> (raw)
In-Reply-To: <1117561043.4455.1.camel@dhcp83-8.boston.redhat.com>

On Tue, May 31, 2005 at 01:37:23PM -0400, Ivan Gyurdiev wrote:
> 
> > Problem is that they both want to create directly in /tmp.  It would be
> > preferable if they had a dedicated subtree, e.g. /tmp/gconfd
> > and /tmp/orbit, with all per-user subdirectories underneath, so that the
> > top-level directory could be typed separately and set up a priori (at
> > boot if truly under /tmp, as they might otherwise have been deleted).
> 
> So you're saying that the directories should be created ahead of time by
> a startup script, and restorecon executed on them... something 
> like tmpskel? Maybe that can be used for libICE, which I want to
> label /tmp/.ICE-unix as ice_tmp_t.
 
 there is a whole slew of legacy applications that assume
 access to /tmp/.ICE-unix, /tmp/.X11-unix etc.

 it's a known problem for which the solution - creating tmp
 subdirectories - has been "scheduled" / "shelved".

 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.

  parent reply	other threads:[~2005-05-31 21:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-28  3:09 file_type_auto_trans is not sufficient Ivan Gyurdiev
2005-05-28  3:47 ` Ivan Gyurdiev
2005-05-28  5:24   ` Daniel J Walsh
2005-05-29  3:17     ` Ivan Gyurdiev
2005-05-29 10:52       ` Daniel J Walsh
2005-05-29 17:44         ` Ivan Gyurdiev
2005-05-30  3:03           ` Ivan Gyurdiev
2005-05-30  8:05             ` Ivan Gyurdiev
2005-05-31 13:36               ` Stephen Smalley
2005-05-31 15:09                 ` Ivan Gyurdiev
2005-05-31 13:18 ` Stephen Smalley
2005-05-31 13:35   ` Ivan Gyurdiev
2005-05-31 13:53     ` Stephen Smalley
2005-05-31 14:12     ` Karl MacMillan
2005-05-31 14:57       ` Ivan Gyurdiev
2005-05-31 16:32         ` Karl MacMillan
2005-05-31 16:48           ` Ivan Gyurdiev
2005-05-31 17:07             ` Stephen Smalley
2005-05-31 17:37               ` Ivan Gyurdiev
2005-05-31 17:39                 ` Stephen Smalley
2005-05-31 18:05                   ` Ivan Gyurdiev
2005-05-31 21:10                 ` Luke Kenneth Casson Leighton [this message]
2005-05-31 21:12             ` Luke Kenneth Casson Leighton
2005-05-31 21:21         ` Luke Kenneth Casson Leighton
2005-05-31 21:21           ` Luke Kenneth Casson Leighton
2005-05-31 23:09           ` Chad Sellers
2005-06-01  0:02             ` Luke Kenneth Casson Leighton
2005-06-01 11:21           ` Stephen Smalley
2005-06-01 11:21             ` 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=20050531211027.GD11815@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=ivg2@cornell.edu \
    --cc=kmacmillan@tresys.com \
    --cc=sds@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.