From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: James Morris <jmorris@redhat.com>, SELinux <SELinux@tycho.nsa.gov>
Subject: Re: Problems with MCS/Targeted policy update.
Date: Wed, 24 Aug 2005 11:14:00 -0400 [thread overview]
Message-ID: <430C8EB8.80906@redhat.com> (raw)
In-Reply-To: <1124893226.11553.32.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>On Wed, 2005-08-24 at 09:34 -0400, Daniel J Walsh wrote:
>
>
>>I would like to be able to upgrade rawhide with a new targeted policy
>>containing MCS. I see a couple of problems when I do this.
>>
>>The number one problem, it that it still requires an relable. Even
>>though the latest kernel defaults everything to level of "sid file"
>>getfilecon or the kernel is is still reading the file context off disks
>>without the "s0" so the kernel is reporting hundreds of invalid
>>contexts, need to figure a way to fix this or we will need a relabel.
>>(Relabeling when upgrading from FC4-FC5 will not be pretty).
>>
>>
>
>What is the exact error message? Given the change made by James, the
>kernel shouldn't be getting any error from
>security_context_to_sid_default and thus shouldn't be logging a warning
>about the contexts. What kernel are you running?
>
>
>
Must have been a older kernel. Just tried it again with
2.6.12-1.1505_FC5 and it seems to work.
chcon is broken though, ls and other commands are not getting the :s0
since it is not there, so there might be other problems,
>>Certain applications like chcon, might need to change to use _raw
>>functions, _raw function/options would be nice to add to certain
>>coreutils, at least for debugging purposes.
>>
>>
>
>You certainly don't want them to use the raw functions by default, but
>having it as an option might be useful.
>
>
>
--
--
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.
next prev parent reply other threads:[~2005-08-24 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 13:34 Problems with MCS/Targeted policy update Daniel J Walsh
2005-08-24 14:20 ` Stephen Smalley
2005-08-24 15:14 ` Daniel J Walsh [this message]
2005-08-25 14:44 ` Stephen Smalley
2005-08-25 15:12 ` Stephen Smalley
2005-08-25 15:19 ` Karl MacMillan
2005-08-25 16:14 ` Stephen Smalley
2005-08-25 18:13 ` Karl MacMillan
2005-08-26 18:16 ` Daniel J Walsh
2005-08-26 18:24 ` Stephen Smalley
2005-08-26 18:50 ` Daniel J Walsh
2005-08-26 18:55 ` Stephen Smalley
2005-08-26 18:51 ` Daniel J Walsh
2005-08-26 18:25 ` Daniel J Walsh
2005-08-26 18:27 ` Stephen Smalley
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=430C8EB8.80906@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=jmorris@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.