All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Ivan Gyurdiev <gyurdiev@redhat.com>
Cc: Karl MacMillan <kmacmillan@tresys.com>,
	"'Stephen Smalley'" <sds@tycho.nsa.gov>,
	"'Joshua Brindle'" <jbrindle@tresys.com>,
	"'Daniel J Walsh'" <dwalsh@redhat.com>,
	"'SELinux'" <selinux@tycho.nsa.gov>,
	selinux-dev@tresys.com
Subject: Re: Restorecon script
Date: Fri, 10 Jun 2005 21:18:14 +0100	[thread overview]
Message-ID: <20050610201814.GB8525@lkcl.net> (raw)
In-Reply-To: <1118427661.3720.36.camel@dhcp83-8.boston.redhat.com>

On Fri, Jun 10, 2005 at 02:21:01PM -0400, Ivan Gyurdiev wrote:
> >  If the files are under the user's
> > control then they should be fully under their control. 
> 
> The way to do that is by integrating ugly libselinux code into
> a large number of applications. I think this will not be 
> well received by the upstream developers at this time.
 
 at some point, i believe that they are going to have to.

 developers use "chown()" and "chgrp()" etc. all the time.

 the people developing selinux have done a _great_ job designing
 something that covers nearly all of the cases.

 ... idea for you.
 
 how about "auto-file-domaining" on chown() and chgrp(), in
 a similar way that exec() performs auto-domain-transitioning?

 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-06-10 20:18 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09 14:41 Restorecon script Ivan Gyurdiev
2005-06-10  2:11 ` Joshua Brindle
2005-06-10  2:32   ` Ivan Gyurdiev
2005-06-10 13:52     ` Steve G
2005-06-10 18:04       ` Ivan Gyurdiev
2005-06-10 16:05     ` Joshua Brindle
2005-06-10 16:11       ` Stephen Smalley
2005-06-10 17:44         ` Karl MacMillan
2005-06-10 17:41           ` Stephen Smalley
2005-06-10 18:01             ` Ivan Gyurdiev
2005-06-10 18:06             ` Karl MacMillan
2005-06-10 18:04               ` Stephen Smalley
2005-06-10 18:59                 ` Karl MacMillan
2005-06-10 18:21               ` Ivan Gyurdiev
2005-06-10 19:58                 ` Karl MacMillan
2005-06-10 20:45                   ` Ivan Gyurdiev
2005-06-10 21:05                     ` Karl MacMillan
2005-06-10 21:47                       ` Ivan Gyurdiev
2005-06-11 17:45                         ` Karl MacMillan
2005-06-11 18:35                           ` Ivan Gyurdiev
2005-06-10 20:18                 ` Luke Kenneth Casson Leighton [this message]
2005-06-10 20:54                   ` Ivan Gyurdiev
2005-06-10 21:05                   ` Valdis.Kletnieks
2005-06-10 21:42                     ` Luke Kenneth Casson Leighton
2005-06-10 21:03                 ` Joshua Brindle
2005-06-10 21:30                   ` Ivan Gyurdiev
2005-06-11 18:00                     ` Karl MacMillan
2005-06-10 17:58       ` Ivan Gyurdiev
2005-06-10 18:19         ` Karl MacMillan
2005-06-10 18:31           ` Ivan Gyurdiev
2005-06-10 19:45             ` Karl MacMillan
2005-06-10 20:57               ` Ivan Gyurdiev
2005-06-10 21:09                 ` Karl MacMillan
2005-06-10 20:26             ` Luke Kenneth Casson Leighton
2005-06-10 21:57               ` Ivan Gyurdiev
2005-06-10 22:11                 ` Luke Kenneth Casson Leighton
2005-06-10 20:21           ` Luke Kenneth Casson Leighton
2005-06-11  0:09             ` Valdis.Kletnieks
2005-06-11  1:13               ` Casey Schaufler
2005-06-10 15:15 ` Stephen Smalley
2005-06-10 15:38   ` Stephen Smalley
2005-06-10 17:15     ` Ivan Gyurdiev
2005-06-10 17:12   ` Ivan Gyurdiev
2005-06-10 15:18 ` Stephen Smalley
2005-06-10 17:52   ` Ivan Gyurdiev
2005-06-10 20:23     ` Luke Kenneth Casson Leighton
2005-06-10 21:59       ` Ivan Gyurdiev

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=20050610201814.GB8525@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=dwalsh@redhat.com \
    --cc=gyurdiev@redhat.com \
    --cc=jbrindle@tresys.com \
    --cc=kmacmillan@tresys.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux-dev@tresys.com \
    --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.