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-dev@tresys.com, SELinux@tycho.nsa.gov, dwalsh@redhat.com
Subject: Re: [ SEMANAGE ] Install seusers, rename some files
Date: Tue, 01 Nov 2005 16:12:28 -0500	[thread overview]
Message-ID: <4367DA3C.3020308@cornell.edu> (raw)
In-Reply-To: <1130877661.22731.308.camel@moss-spartans.epoch.ncsc.mil>

>
> I think moving the local files into the sandbox upon policy update (via
> %post scriptlet in the policy package) is reasonable, as this is only
> needed for migration and will not be done subsequently.
I guess at that point we also want to migrate booleans.local, 
local.users, and install the base module?
Dan, can you add such a script?

- copy /etc/selinux/?/seusers into /etc/selinux/?/modules/active/seusers
- copy /etc/selinux/?/local.users into 
/etc/selinux/?/modules/active/users.local [ renamed ]
- copy /etc/selinux/?/booleans.local into 
/etc/selinux/?/modules/active/booleans.local
- install base module into /etc/selinux/?/modules/active/base.pp (is 
this managed by rpm?)
> Yes.  But we need to avoid breaking use of semodule -b now via this
> patch until such a time as the seusers support is in place, so possibly
> I should just change the error handling here to just WARN and proceed
> with the reload.
Hmm... that sounds reasonable... I think.

--
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 21:12 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
2005-11-01 20:41     ` Stephen Smalley
2005-11-01 21:12       ` Ivan Gyurdiev [this message]
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=4367DA3C.3020308@cornell.edu \
    --to=ivg2@cornell.edu \
    --cc=SELinux-dev@tresys.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dwalsh@redhat.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.