From owner-freebsd-hackers Fri Oct 18 09:08:13 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA04122 for hackers-outgoing; Fri, 18 Oct 1996 09:08:13 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA04117; Fri, 18 Oct 1996 09:08:08 -0700 (PDT) Message-Id: <199610181608.JAA04117@freefall.freebsd.org> To: matthew green cc: jdp@polstra.com, ache@nagual.ru, guido@gvr.win.tue.nl, thorpej@nas.nasa.gov, phk@critter.tfs.com, freebsd-hackers@freebsd.org, tech-userlevel@netbsd.org, Karl Denninger Subject: Re: cvs commit: src/lib/libc/db/hash hash_buf.c In-reply-to: Your message of "Fri, 18 Oct 1996 18:47:09 +1000." <199610180847.SAA17954@eterna.com.au> Date: Fri, 18 Oct 1996 09:08:07 -0700 From: "Justin T. Gibbs" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > >A program which calls setuid() isn't SUID any more. Once done, that's > >terminal (and can't be "recalled"). > > The saved UID is not perterbed which allows you to determine that the > program was setuid. > >setuid() changes the effective, real and saved user ids. RTFM if you >don't believe me. I miss read a portion of the daemon book, my appologies. >the correct way to check if a process was started setuid or setgid is >to check the SUGID flag. I should have simply looked at the source. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations ===========================================