Miscellaneous > Technical Support

FC4 is fucked

<< < (2/2)

mobrien_12:
I'm not an SELinux expert, but it's pretty cool from what I've read about it.  You know how basically with *nix systems if root gets compromised you are totally hosed?  Well SELinux puts controls on root so cracking root means the entire system isn't compromised.  It's a whole new quantum level of security, but because it puts limits on root, it can cause problems when misconfigured.

Did you do ANYTHING to the box?  Update RPMS?  install something?  What do your system logs say?

Does tripwire say anything has changed?

H_TeXMeX_H:
Only way my system may have been compromised was through sendmail ... which I have chosen not to install on FC5, but was there on FC4.

Prior to this crash I updated the system as usual ... yum update --exclude=kernel (I was running an older kernel to stay away from the ambiguous "..MP-BIOS bug: 8254 timer not connected to IO-APIC" error). I also messed around a bit with the grub.config adding the noapic flag to the newer, buggy kernel ... I think this may have a lot to do with it. It booted fine with noapic the first time ... the night before it screwed up, then I removed the noapic, and it also booted fine, and then it didn't boot fine in the morning.

cymon:
Mabye FC is the problem, not SELinux.

H_TeXMeX_H:
Possible ... I now keep some live CDs around just in case it happens again. I used to have Knoppix and DSL around, but I loaned them to a friend to try em out ... hey I wasn't using them too much. But I just burned another copy of DSL. DSL is the best damn live CD ever ... it's so damn fast (especially if you write it to ram) :thumbup: ... now if only I could run OpenOffice 2.0 on it ... I'll figure something out.

mobrien_12:
I have never seen this with FC4.

Navigation

[0] Message Index

[*] Previous page