full-disclosure - Re: [Dailydave] R. RHEL, RHCS, and Selinux : hype, reality or dream?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <90691a990910090728x10c8f83blc1e6a01ed5ea7f1@mail.gmail.com>
Date: Fri, 9 Oct 2009 16:28:43 +0200
From: Marco Ermini <marco.ermini@...il.com>
To: yersinia <yersinia.spiros@...il.com>
Cc: full-disclosure <full-disclosure@...ts.grok.org.uk>,
	dailydave <dailydave@...ts.immunitysec.com>
Subject: Re: [Dailydave] R. RHEL, RHCS, and Selinux : hype,
	reality or dream?

2009/9/9 yersinia:
> So it seems that it is not necessary to be a clever hacker as spender to
> disable SELinux on a system (http://grsecurity.net/~spender/exploit.txt).
> Just follow the directions of the vendor. This one require to disable
> selinux for the proper function of one of its HA products, after years that
> the same vendor was critical with commercial product, o badly compiled open
> source for SELINUX execmem o textreloc issue,  because they require the
> same.
[...]

It is just necessary to install an updated SELinux policy to make the
RH Cluster work with SELinux.

https://bugzilla.redhat.com/attachment.cgi?id=348662

I guess the fault is mainly in the vendor documentation...


Cheers
-- 
Marco Ermini
root@...an # mount -t life -o ro /dev/dna /genetic/research
http://www.linkedin.com/in/marcoermini
"Jesus saves... but Buddha makes incremental back-ups!"

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/