From: "Dirk Heinrichs" <dirk.heinrichs@online.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Block root user from login on xorg GUI
Date: Sun, 15 Nov 2009 10:22:20 +0100 [thread overview]
Message-ID: <200911151022.25803.dirk.heinrichs@online.de> (raw)
In-Reply-To: 200911150050.42839.alan.mckinnon@gmail.com
[-- Attachment #1: Type: Text/Plain, Size: 1813 bytes --]
Am Samstag 14 November 2009 23:50:42 schrieb Alan McKinnon:
> On Saturday 14 November 2009 22:46:18 Dirk Heinrichs wrote:
> > Am Samstag 14 November 2009 16:13:04 schrieb Nikos Chantziaras:
> > > Ever heard about make menuconfig?
> >
> > ???
>
> The account foolishly being "prevented" from bypassing SELinux is root.
>
> So, configure a new kernel, disable SELinux, build, install, reboot.
>
> Voila! No SELinux.
>
> Or,
>
> Edit grub.conf, reboot.
>
> Voila! No SELinux.
>
> Or, (as SELinux can be used to prevent access to grub.conf)
>
> Just hit the damn power button and edit the kernel options in the grub
> command line.
Compile in kernel options, configure the kernel not to accept additional ones.
Damn power button rendered useless.
> Trying to prevent root from doing $STUFF on a pc is utterly and completely
> pointless and simply will not succeed, ever. There is hardware where this
> can be done, but it's not a PC, has no Intel designs in it and is often
> truly secured with armed guards.
This all implies physical access to the machine, right?
> trying to prevent root from doing $STUFF on Unix is utterly and completely
> pointless and simply will not succeed, ever. There are OSes where this can
> be done, but they are not Unix. By definition, on Unix root can do
> anything, including bypassing systems to prevent root from doing anything.
SELinux allows to spread the tasks root needs to do or can do accross several
roles. Of course, if only one single person has root access to the system this
doesn't make sense. But we're talking about cases where several people (incl.
the malicious attacker) have root access. So you can very well configure a
(SE-)Linux system so that "root" can't do everything.
Bye...
Dirk
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2009-11-15 10:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 20:01 [gentoo-user] Block root user from login on xorg GUI Mick
2009-11-12 20:39 ` Dirk Heinrichs
2009-11-12 20:56 ` Mick
2009-11-12 21:08 ` Dirk Heinrichs
2009-11-12 21:34 ` Paul Hartman
2009-11-12 21:46 ` Mick
2009-11-12 21:56 ` Alan McKinnon
2009-11-12 22:15 ` Mick
2009-11-13 15:39 ` Paul Hartman
2009-11-12 22:09 ` Alan McKinnon
2009-11-12 22:18 ` Mick
2009-11-12 23:08 ` Iain Buchanan
2009-11-13 2:45 ` Zeerak Waseem
2009-11-14 0:24 ` Mick
2009-11-14 7:01 ` Joshua Murphy
2009-11-14 7:07 ` Joshua Murphy
2009-11-14 19:32 ` Mick
2009-11-14 20:46 ` Alan McKinnon
2009-11-15 5:15 ` Stroller
2009-11-15 7:44 ` Dale
2009-11-15 8:26 ` Alan McKinnon
2009-11-15 12:47 ` Stroller
2009-11-15 15:11 ` Alan McKinnon
2009-11-15 8:52 ` Neil Bothwick
2009-11-15 10:52 ` Alan McKinnon
2009-11-15 13:37 ` Neil Bothwick
2009-11-14 9:21 ` [gentoo-user] " Nikos Chantziaras
2009-11-14 10:12 ` Dirk Heinrichs
2009-11-14 15:13 ` Nikos Chantziaras
2009-11-14 19:30 ` Alan McKinnon
2009-11-14 20:46 ` Dirk Heinrichs
2009-11-14 22:50 ` Alan McKinnon
2009-11-15 9:22 ` Dirk Heinrichs [this message]
2009-11-15 14:40 ` Nikos Chantziaras
2009-11-15 16:12 ` Alan McKinnon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200911151022.25803.dirk.heinrichs@online.de \
--to=dirk.heinrichs@online.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox