2009/9/9 James Morris <jmorris@xxxxxxxxx>
Thanks for pointing this out -- I was not aware of this.
> Hi. Sorry in advance for the polemical tone and the topic that is not
> technical.
This issue is being worked on.
The tracking bz entry for this is:
https://bugzilla.redhat.com/show_bug.cgi?id=503141
Ok, i already know. BUT now, i that have 100+ RHEL 5.4 with RHCS with Selinux enforced in a critical env AND want a certificated configuration what i have to do ? Disable it everywhere ? It 'a very bad message, which, in my opinion, should be resolved VERY quickly.
BTW, with RHEL5.4 no problem, also minor, with RHCS, but the manual tell me to do something different. It 'a very bad message from a selinux product (
, which, in my opinion, should be resolved very quickly. IMHO, should be preferable that the rhcs daemon go unconfined, if the selinux policy aren't complete, rather than requiring to disable selinux everywhere.
Just for info : this post is already refenced on other mailing list
Regards
- James
--
James Morris
<jmorris@xxxxxxxxx>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
