currupt policy.11 file
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 6 lines · you
I accidently currupted my policy.11 file, probably by loading it before it had been fully written (yes, stupid thing to do).
Anyway, the effect of this was my computer promptly crashed. By this I mean it was running extremely slowly, and eventually refused to respond to any user input.
Should have a checksum or something.
Quoted 7 lines
So I rebooted it.
It tried to load the currupted policy and crashed again.
If I left it a while the kernel complained it was out of memory, and it had no processes it could kill.
Quoted 7 lines
So I suspect there might be a bug somewhere...
I had to boot from an old kernel without SE-Linux support to rectify the problem.
Anyway, is there anyway to boot a computer without loading a faulty policy?
Boot a non-SE kernel, or a SE kernel that uses an older version of the policydb.
Quoted 3 lines
Actually, this might still be a problem, because you can't login without a policy present, but I guess at least you should be able to boot with init=/bin/sh.
Unless you have a policydb in an initrd and boot using that...
Quoted 1 line
I still have a copy of this bad policy.11 file if you want a copy.
You are probably better off sending such messages to the list direct...
Signature · 3 lines
I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line
From field.
--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 7 lines · Russell Coker
Quoted 6 lines · you
I accidently currupted my policy.11 file, probably by loading it before it had been fully written (yes, stupid thing to do).
Anyway, the effect of this was my computer promptly crashed. By this I mean it was running extremely slowly, and eventually refused to respond to any user input.
I'd be interested in obtaining a copy of the corrupted policy.11 file so that I can try to reproduce the error. I just tried loading a truncated policy.11 file (both a truncated compressed policy.11 and a truncated uncompressed policy.11), and in both cases, the security server reported an appropriate error during the load and continued operating under the old policy.
--
Stephen D. Smalley, NAI Labs
[email protected]
--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.