All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: ivg2@cornell.edu
Cc: russell@coker.com.au, SELinux <SELinux@tycho.nsa.gov>
Subject: Re: [Fwd: Latest Diff]
Date: Mon, 09 May 2005 14:17:07 -0400	[thread overview]
Message-ID: <427FA923.9010906@redhat.com> (raw)
In-Reply-To: <1115662376.10218.16.camel@localhost.localdomain>

Ivan Gyurdiev wrote:

>>I am not crazy about this patch.  Since I don't think we need to run a 
>>priveledged orbit. 
>>    
>>
>
>orbit is not privileged - there will be no orbit domain - 
>it's just a file type with some macros to mark the appropriate sockets,
>and allow connections between them.
>
>The benefit of this is that:
>
>(1) Applications no longer access ROLE_tmp_t, 
>they access ROLE_orbit_tmp_t instead, which is a more
>specific type for this operation, separate from the type
>that would be used for other things.
>
>(2) Once things are properly confined they will not need
>to access ROLE_orbit_tmp_t either, which is really the point of 
>this patch - proper labeling of orbit sockets for each 
>application. Already gift is disallowed access to anything but 
>gconf orbit sockets. This doesn't work for mozilla yet, because 
>it talks to gnome-vfs-daemon, and other things, but eventually 
>all of them should be confined. 
>
>(3) This removes generic types, and adds more specific ones.
>I see this as a step forward.
>
>See the patches I sent for the implementation.
>
>  
>
>>If we have the init scripts create a /tmp/orbit directory and the login 
>>creates orbit-$USER
>>under there we can get all the transitions correct.  Can't we?
>>    
>>
>
>So, do you oppose the whole patch, or just the part the makes
>orbit depend on libselinux?
>
>I'm not sure about a startup script - that's a possible solution,
>but Bill Nottingham didn't like my /tmp skeleton idea, and after
>a while I thought it would be better to do this in the application
>as well.
>
>With a startup script, we have to create the folder for all users,
>regardless of whether they need it. Also, orbit
>creates /tmp/orbit-$USER-(random hex number) for some reason,
>and I haven't figured out why it does that yet. Also, tmpwatch
>might erase that folder due to inactivity (and maybe it should
>be able to). If that happens, we don't want to have to reboot
>to recreate it. 
>
>  
>
Doesn't you patch mean that every app that links with orbit needs to 
able to read context files
and able to setfscreatecon?

Dan

-- 



--
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:[~2005-05-09 18:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 19:35 [Fwd: Latest Diff] Daniel J Walsh
2005-05-05 21:44 ` Ivan Gyurdiev
2005-05-06  1:34   ` Russell Coker
2005-05-06  1:58     ` Ivan Gyurdiev
2005-05-06 15:39       ` Ivan Gyurdiev
2005-05-07 13:50         ` Russell Coker
2005-05-07 17:04           ` Ivan Gyurdiev
2005-05-07 19:50             ` Ivan Gyurdiev
2005-05-09 14:42               ` Daniel J Walsh
2005-05-09 18:12                 ` Ivan Gyurdiev
2005-05-09 18:17                   ` Daniel J Walsh [this message]
2005-05-09 18:24                     ` Ivan Gyurdiev
2005-05-09 18:27                       ` Daniel J Walsh
2005-05-09 18:37                         ` Ivan Gyurdiev
2005-05-11 14:59                           ` Stephen Smalley
2005-05-07 23:01             ` Russell Coker
2005-05-06 12:33   ` Daniel J Walsh
2005-05-06  5:33 ` Russell Coker
2005-05-06 12:43   ` Daniel J Walsh
2005-05-06 13:22     ` 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=427FA923.9010906@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=ivg2@cornell.edu \
    --cc=russell@coker.com.au \
    /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.