From: Daniel J Walsh <dwalsh@redhat.com>
To: John Reuning <john@metalab.unc.edu>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Fedora Core 2 Test 2
Date: Fri, 09 Apr 2004 11:25:14 -0400 [thread overview]
Message-ID: <4076C05A.6010104@redhat.com> (raw)
In-Reply-To: <1081481682.11877.26.camel@camelot>
John Reuning wrote:
>I'll offer my limited experience with fc2t2. I've done two installs,
>both onto clean systems with reformatted partitions. There was an
>option to disable selinux in the installer click-through choices.
>
>The first install resulted in an almost unusable system. I think
>something hiccuped because the fs labeling was messed up. For example,
>I couldn't create user accounts as root because the root user didn't
>have access to write /etc/shadow or /etc/passwd. A manual relabeling of
>the file systems fixed the problem. After that, everything was fine.
>
>The second install was smooth. No labeling or policy problems yet.
>Although, I haven't used the system except as a headless test server.
>
>I haven't tried upgrading a fc1 system to fc2t2. Maybe that's a source
>of trouble?
>
>Thanks,
>
>-John R.
>
>
>
First off there is a Mailing list for discussing Fedora SELinux issues.
http://www.redhat.com/mailman/listinfo/fedora-selinux-list
As well as fedora-test-list and fedora-devel-list (Discussions are going
on all three lists).
1. Upgrading to Fedora Core 2/SELinux requires a relabel of the file
system, so people
who have done this have gotten into trouble.
2. We have had tons of fixes to policy over the past few weeks that
have cleaned up a lot of
problems. So if you install FC2, make sure you update to the latest
policy off of rawhide.
3. Overall the number of bugs being reported has dropped dramatically,
either we have fixed
a lot of the problems or people have figured out how to turn off SELinux
(Probably a combination
of both.)
4. Red Hat will be announcing our strategy for SELinux support in
FC2/Test3 and Final shortly.
>>>1: I was a little surprised to find that SELinux was installed by
>>>default and that there didn't seem to be a way to avoid it. This said,
>>>the kernel did come up properly and the system booted.
>>>[snip]
>>>
>>>
>
>
>
The installer has three options currently Enforcing (Default),
Permissive, Disabled.
There is also a FAQ explaining how to use SELinux within FC2.
http://people.redhat.com/kwade/fedora-docs/selinux-faq-en/
Comments welcome.
>
>--
>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.
>
>
--
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:[~2004-04-09 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 21:27 Fedora Core 2 Test 2 Nick Gray
2004-04-09 0:11 ` Kerry Thompson
2004-04-09 3:34 ` John Reuning
2004-04-09 15:25 ` Daniel J Walsh [this message]
2004-04-12 7:28 ` Russell Coker
2004-04-14 9:02 ` Tom
2004-04-15 11:05 ` Wesley Parish
2004-04-09 12:03 ` 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=4076C05A.6010104@redhat.com \
--to=dwalsh@redhat.com \
--cc=john@metalab.unc.edu \
--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.