|Main Archive Page > Month Archives > selinux archives|
Is anyone here familiar with the work that IBM is doing on ticket RATLC00762574 in their Rational ClearCase issue queue?
See item 9 here:
"Secure Linux (SELinux) and ClearCase
If the security feature of Linux known as SELinux is enabled on a ClearCase host, normal operations can fail. ClearCase is currently not supported on Secure Linux (SELinux). Change request RATLC00762574 has been submitted requesting support for ClearCase on SELinux."
There is a request for more information from IBM on this but I figured I would try to get some input from this list as well.
Apparently there are some inconsistencies in the way MVFS filesystems interact with SELinux filesystems (or at the very least when in the config file, "SELINUX=enabled") and so I can foresee an organization hitting the wall with RHEL4 rollouts, finding out late in the game.
Basically to sum up my own specific experience: A /bin/mv operation fails from an ext3 partition on an SELinux enabled RHEL4 box ("mv: cannot create regular file", "Permission denied") to an MVFS filesystem -but- a copying (/bin/cp) operation from ext3 to MVFS works fine, no problems whatsoever (given requisite perms, of course).
So, disable SELinux, and the move operation is back to normal.
Previous versions of mv (from RHEL3) still work while in
"SELinux=enabled" mode, but negates the RHEL4 baseline integrity, so
while that may be a workaround for some, its obviously not a real fix for all.
Would anyone care to lend some extra info either via the list or perhaps offline with me?
Jay C. James
"no extra charge applied for typos or formatting annoyances"
-- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to firstname.lastname@example.org with the words "unsubscribe selinux" without quotes as the message.