Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Jul 1998 10:27:08 -0500 (EST)
From:      Alfred Perlstein <bright@hotjobs.com>
To:        Stephen Hocking-Senior Programmer PGS Tensor Perth <shocking@prth.pgs.com>
Cc:        hackers@FreeBSD.ORG
Subject:   Re: How do you tell (within the kernel) if we started setuid?
Message-ID:  <Pine.BSF.3.96.980714102640.5923F-100000@bright.ny.otec.com>
In-Reply-To: <199807140237.KAA10232@ariadne.tensor.pgs.com>

next in thread | previous in thread | raw e-mail | index | archive | help
don't crosspost please.

NAME
     issetugid - is current process tainted by uid or gid changes    

DESCRIPTION
     The issetugid() function returns 1 if the process environment or
memory
     address space is considered ``tainted'', and returns 0 otherwise.

     A process is tainted if it was created as a result of an execve(2)
system
     call which had either of the setuid or setgid bits set (and extra
privi-
     leges were given as a result) or if it has changed any of it's real,
ef-
     fective or saved user or group ID's since it began execution.     


-alfred

On Tue, 14 Jul 1998, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:

> 
> If you're executing a program that was started setuid root but has 
> subsequently given up its privileges, is there anyway to tell if it was 
> originally set uid?
> 
> 
> 	Stephen
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980714102640.5923F-100000>