Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Dec 2004 21:21:51 -0600
From:      Scott Gerhardt <scott@g-it.ca>
To:        bv@wjv.com
Cc:        freebsd-security@freebsd.org
Subject:   Re: Strange command histories in hacked shell history
Message-ID:  <F561011D-50A3-11D9-BD27-000393801C60@g-it.ca>
In-Reply-To: <20041218022556.GA85192@wjv.com>
References:  <20041217120138.7A89116A4D2@hub.freebsd.org> <20041217145315.GB68582@wjv.com> <41C391BE.3030604@earthlink.net> <20041218022556.GA85192@wjv.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> I understand that after using Unix for about 2 decades.
> However in FreeBSD a user is supposed to be in the wheel group [if
> it exists] to be able to su to root.
>
> But if a person who is not in wheel su's to a user who is in wheel,
> then they can su to root - as the system sees them as the other
> user.  This means that the 'wheel' security really is nothing more
> than a 2 password method to get to root.
>
> If the EUID of the orignal invoker is checked, even if they su'ed
> to a person in wheel, then they should not be able to su to root.
>
> I'm asking why is this permitted, or alternatively why is putting a
> user in the wheel group supposed to make things secure, when in
> reality it just makes it seem more secure - as there is only one
> more password to crack.
>

This makes no sense.  If you can su to a user in the wheel group as an 
unprivileged user you need to know the users password and you also need 
to know roots password to su to root.  This seems pretty secure to me.

If you want to be more secure than this then use sudo.


--
Scott



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F561011D-50A3-11D9-BD27-000393801C60>