All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <method@manicmethod.com>
To: casey@schaufler-ca.com
Cc: russell@coker.com.au, Stephen Smalley <sds@tycho.nsa.gov>,
	selinux@tycho.nsa.gov
Subject: Re: [RFC][PATCH] selinux:  enable authoritative granting of capabilities
Date: Thu, 14 Jun 2007 10:50:01 -0400	[thread overview]
Message-ID: <46715599.7070300@manicmethod.com> (raw)
In-Reply-To: <558323.22266.qm@web36612.mail.mud.yahoo.com>

Casey Schaufler wrote:
> --- Russell Coker <russell@coker.com.au> wrote:
>
>   
>> On Wednesday 13 June 2007 22:31, Stephen Smalley <sds@tycho.nsa.gov> wrote:
>>     
>>> On Wed, 2007-06-13 at 21:16 +1000, Russell Coker wrote:
>>>       
>>>> On Wednesday 13 June 2007 01:57, Stephen Smalley <sds@tycho.nsa.gov> 
>>>>         
>> wrote:
>>     
>>>>> Well, first, no script should be allowed a capability that is not given
>>>>> to its caller directly ;)
>>>>>           
>>>> Why not?  Isn't that the entire point of this authoritative granting of
>>>> capabilities patch?
>>>>         
>>> _script_, not program.
>>>       
>> OK, that's a bit of a topic change.
>>
>> I've been thinking about the script issue.  It seems to me that a problem we 
>> face is the replacement of executables by scripts (which often happens in 
>> distributions and sometimes happens with programs that are relevant to system
>>
>> integrity).
>>     
>
> That should only be a problem on a name based system, right?
>
> OK, sorry for the dig. Anyhow, it seems that the program that
> sets the policy (labels the file system?) ought to be checking
> the "type" of the file if it matters. You also might consider
> that as 21st century programming (special purpose scripting)
> replaces 20th century programming (general purpose binaries)
> fewer people are going to be tolerent of a distintion between
> a "program" and a "script" and look seriously at how you might
> avoid having to treat them differently.
>   

We don't have to treat them differently if the interpreters will respect 
ATSECURE and cleanse the environment across domain transitions or setuid 
just like the linker does for compiled binaries. The race will still be 
there but is alot harder to exploit than environment changes that change 
the interpreter behavior.

--
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:[~2007-06-14 14:50 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 19:55 [RFC][PATCH] selinux: enable authoritative granting of capabilities Stephen Smalley
2007-06-11 20:39 ` James Morris
2007-06-11 20:43 ` Serge E. Hallyn
2007-06-11 21:43   ` Casey Schaufler
2007-06-11 22:20     ` James Morris
2007-06-12  0:00       ` Casey Schaufler
2007-06-12 11:46         ` Stephen Smalley
2007-06-11 22:24     ` Serge E. Hallyn
2007-06-12  9:20       ` Russell Coker
2007-06-12 15:44         ` Serge E. Hallyn
2007-06-12 15:57           ` Stephen Smalley
2007-06-13 11:16             ` Russell Coker
2007-06-13 12:31               ` Stephen Smalley
2007-06-14  9:44                 ` Russell Coker
2007-06-14 11:03                   ` Stephen Smalley
2007-06-14 14:50                     ` Stephen Smalley
2007-06-14 14:54                       ` Joshua Brindle
2007-06-14 13:54                   ` Casey Schaufler
2007-06-14 14:50                     ` Joshua Brindle [this message]
2007-06-14 15:05                       ` Stephen Smalley
2007-06-12 11:43       ` Stephen Smalley
2007-06-12 11:31     ` Stephen Smalley
2007-06-12  9:27   ` Russell Coker
2007-06-12 12:09     ` Stephen Smalley
2007-06-12 12:50 ` Stephen Smalley
2007-06-12 15:08   ` Casey Schaufler
2007-06-12 15:33     ` Stephen Smalley
2007-06-12 16:38       ` Casey Schaufler
2007-06-12 17:49         ` James Morris
2007-06-12 19:56           ` Casey Schaufler
2007-06-12 16:03   ` Serge E. Hallyn
2007-06-12 13:24 ` Stephen Smalley
2007-06-12 20:50   ` Stephen Smalley
2007-06-12 21:12     ` Stephen Smalley
2007-06-13 14:31       ` Stephen Smalley
2007-06-13 15:06         ` Christopher J. PeBenito
2007-06-13 15:28           ` Stephen Smalley
2007-06-13 18:46             ` Christopher J. PeBenito
2007-06-13 19:20               ` Stephen Smalley
2007-06-14 19:19                 ` Christopher J. PeBenito
2007-06-15 11:50                   ` Stephen Smalley
2007-06-13 19:10             ` Eric Paris
2007-06-13 19:22               ` Stephen Smalley
2007-06-13 19:50                 ` Daniel J Walsh
2007-06-13 20:00                   ` Stephen Smalley
2007-06-13 20:22                     ` Daniel J Walsh
2007-06-12 13:32 ` Stephen Smalley
2007-06-14 15:40   ` Chad Sellers
2007-06-14 15:55     ` Stephen Smalley
2007-06-14 16:03       ` Stephen Smalley
2007-06-14 16:13         ` Karl MacMillan
2007-06-14 16:52         ` James Morris
2007-06-14 17:28           ` Chad Sellers
2007-06-14 17:35             ` James Morris
2007-06-14 17:43               ` Chad Sellers
2007-06-14 17:47               ` Stephen Smalley
2007-06-14 20:02                 ` Casey Schaufler
2007-06-14 17:46           ` Stephen Smalley
2007-06-14 18:18             ` James Morris
2007-06-14 15:55     ` Karl MacMillan

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=46715599.7070300@manicmethod.com \
    --to=method@manicmethod.com \
    --cc=casey@schaufler-ca.com \
    --cc=russell@coker.com.au \
    --cc=sds@tycho.nsa.gov \
    --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.