| 1 |
On Saturday 14 November 2009 22:46:18 Dirk Heinrichs wrote: |
| 2 |
> Am Samstag 14 November 2009 16:13:04 schrieb Nikos Chantziaras: |
| 3 |
> > Ever heard about make menuconfig? |
| 4 |
> |
| 5 |
> ??? |
| 6 |
|
| 7 |
The account foolishly being "prevented" from bypassing SELinux is root. |
| 8 |
|
| 9 |
So, configure a new kernel, disable SELinux, build, install, reboot. |
| 10 |
|
| 11 |
Voila! No SELinux. |
| 12 |
|
| 13 |
Or, |
| 14 |
|
| 15 |
Edit grub.conf, reboot. |
| 16 |
|
| 17 |
Voila! No SELinux. |
| 18 |
|
| 19 |
Or, (as SELinux can be used to prevent access to grub.conf) |
| 20 |
|
| 21 |
Just hit the damn power button and edit the kernel options in the grub command |
| 22 |
line. |
| 23 |
|
| 24 |
Voila! No SELinux. |
| 25 |
|
| 26 |
Lessons learned: |
| 27 |
|
| 28 |
Trying to prevent root from doing $STUFF on a pc is utterly and completely |
| 29 |
pointless and simply will not succeed, ever. There is hardware where this can |
| 30 |
be done, but it's not a PC, has no Intel designs in it and is often truly |
| 31 |
secured with armed guards. |
| 32 |
|
| 33 |
trying to prevent root from doing $STUFF on Unix is utterly and completely |
| 34 |
pointless and simply will not succeed, ever. There are OSes where this can be |
| 35 |
done, but they are not Unix. By definition, on Unix root can do anything, |
| 36 |
including bypassing systems to prevent root from doing anything. |
| 37 |
|
| 38 |
-- |
| 39 |
alan dot mckinnon at gmail dot com |
Archives