[lkml]   [2001]   [Jul]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectThe SUID bit (was Re: [PATCH] more SAK stuff)
On Thursday 05 July 2001 21:45, Albert D. Cahalan wrote:

> Oh, cry me a river. You can set the RUID, EUID, SUID, and FUID
> in that same parent process or after you fork().

Okay, I'll bite.

The file user ID is fine, the effective user ID is what the suid bit sets to
root of course, the saved user id is irrelevant to this (haven't encountered
something that actually cares about it yet, and yes I have been checking
source code when I bump into a problem).

But the actual uid (real user ID) ain't root, and an euid of root doesn't let
me change the uid itself to root, or at least I haven't figured out how.
(And haven't really tried: there are some things that might conceivably care
whether you really are root or not, but the samba change password command
isn't one of them. I have a password protected cgi accessed via ssl which
allows the manipulation of a limited subset of samba users, and the samba
tool will happily let me change anybody's password as suid root. But to add
a user, the script has to append an entry to the file manually and then
change the password from "racecondition" (which it is) to whatever the user's
password should be. I could patch and ship nonstandard samba binaries, but
that makes automatic upgrades problematic. (And samba, being a net
accessable server, REALLY needs to be kept up to date.))

Do you have a code example of how a program with euid root can change its
actual uid (which several programs check when they should be checking euid,
versions of dhcpcd before I complained about it case in point)?

Some of it's misguided "policy", assuming that the suid bit is on the
executable itself instead of its parent process. A check and an error "Thou
shalt not set this suid root" is fairly common on things that can be securely
run from a daemon running AS root. So apparently, the obvious way to fix it
is to relax the security restrictions even MORE, which is silly.

> Since you didn't set all the UID values, I have to wonder what
> else you forgot to do. Maybe you shouldn't be messing with
> setuid programming.

Ah, the BSD attitude. If you don't already know it, you should die rather
than try to learn it. Anybody who isn't perfect should leave us alone, we
LIKE our user base small. :)

Following this logic, nobody should use Linux because the kernel has
repeatedly shipped with holes allowing people to hack root, gaping big holes
like the insmod `;rm -rf /` thing last year. Apparently we should all be
using an early 90's version of netware or some kind of embedded system
audited for stack overflows and burned in ROM...


(Reference dilbert: "Here's a quarter kid, go buy yourself a real computer."
That's a nice way to recruit new users to help politically support decss or
convince video card manufacturers to release source code to their 3d drivers,
winmodems, funky encryption in USB audio, slipping registration stuff in the
ATA spec...)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:56    [W:0.055 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site