All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux@tycho.nsa.gov
Subject: Re: [ SEMANAGE ] Install seusers, rename some files
Date: Tue, 01 Nov 2005 15:34:02 -0500	[thread overview]
Message-ID: <4367D13A.1050305@cornell.edu> (raw)
In-Reply-To: <1130875837.22731.289.camel@moss-spartans.epoch.ncsc.mil>


> I'm not sure about this; at present, it has the side effect that a
> semodule -b base.pp will fail upon the attempt to copy seusers (because
> there isn't one in the sandbox presently, not even an empty stub).
Yes, the seusers from /etc/selinux/strict/seusers have to get in the 
sandbox somehow...
I'm not entirely sure how, but I think Tresys has indicated that should 
occur through the APIs, rather than by copying it in.

This is only necessary for migration...
>   We also have to be careful about not clobbering any existing seusers file
> during the migration, although I suppose that will be handled by moving
> it into the sandbox upon policy upgrade, as with booleans.local
The authoritative seusers file should be in the sandbox. Personally I 
think all authoritative files should be in the sandbox, and not get 
copied from place to place...  but that's not how things work currently. 
By the way, direct modifications of the /etc/selinux/seusers file will 
be overwritten by libsemanage (but I think the goal is that there should 
be no direct modifications..)

--
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-11-01 20:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01  1:12 [ SEMANAGE ] Install seusers, rename some files Ivan Gyurdiev
2005-11-01 20:10 ` Stephen Smalley
2005-11-01 20:34   ` Ivan Gyurdiev [this message]
2005-11-01 20:41     ` Stephen Smalley
2005-11-01 21:12       ` Ivan Gyurdiev
2005-11-01 21:05         ` Joshua Brindle
2005-11-01 21:42           ` Ivan Gyurdiev
2005-11-01 21:40             ` Stephen Smalley
2005-11-01 21:08         ` Stephen Smalley
2005-11-01 21:11         ` Stephen Smalley
2005-11-01 21:31           ` Ivan Gyurdiev
2005-11-01 21:27             ` Stephen Smalley
2005-11-01 21:15         ` Ivan Gyurdiev
2005-11-01 20:56     ` Ivan Gyurdiev
2005-11-01 21:02       ` Joshua Brindle
2005-11-01 21:10         ` Stephen Smalley
2005-11-01 21:20         ` Ivan Gyurdiev
2005-11-01 21:11           ` Joshua Brindle

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=4367D13A.1050305@cornell.edu \
    --to=ivg2@cornell.edu \
    --cc=SELinux@tycho.nsa.gov \
    --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.