|
BugTraq
Unprivilegued settings for FreeBSD kernel variables Jun 15 2004 06:42AM Radko Keves (rado unitra sk) (3 replies) Re: Unprivilegued settings for FreeBSD kernel variables Jun 18 2004 05:08PM Jason V. Miller (jmiller securityfocus com) Re: Unprivilegued settings for FreeBSD kernel variables Jun 17 2004 11:28AM Manuel Bouyer (bouyer antioche eu org) (2 replies) Re: Unprivilegued settings for FreeBSD kernel variables Jun 18 2004 09:27PM Valdis Kletnieks vt edu (1 replies) Re: Unprivilegued settings for FreeBSD kernel variables Jun 19 2004 09:38PM wietse porcupine org (Wietse Venema) Re: Unprivilegued settings for FreeBSD kernel variables Jun 18 2004 08:25PM Henning Brauer (hb-bugtraq bsws de) Re: Unprivilegued settings for FreeBSD kernel variables Jun 15 2004 07:01PM des des no (Dag-Erling Smørgrav) (2 replies) Re: Unprivilegued settings for FreeBSD kernel variables Jun 17 2004 09:14AM Ivaylo Kostadinov (ivaylo kostadinov computing-services oxford ac uk) |
|
Privacy Statement |
> I've already told you that there is no such threat, since the attack
> you describe can only be initiated by someone who already has
> unrestricted access. Please stop wasting everybody's time.
You are wrong. Unrestricted access means _really unrestricted_ and
kernel securelevel restricts access to certain places even to root.
IMHO, it's dagerous bug, because some administrators can think "...hmm,
I've enabled the hardest securelevel and even if a hacker would break
into my host with r00t privileges he will be restricted in certain ways.
The only thing he can do is to change /etc/rc.conf (for example) and
_reboot_ my host. But I will notice the reboot." So, for certain
people the following formulae may hold:
Hardest securelevel + no reboots = good security.
But this bug changes things. One can lower securelevel, do some nasty things
and raise it again _without reboots_. So, as I've already noted, you are wrong.
The bug _gives_ you almost unrestricted access.
rea
[ reply ]