Subject: weird setuid behavior
To: None <>
From: Niels Provos <>
List: tech-kern
Date: 01/21/2004 01:05:38
I am a bit puzzled by recent changes (last year) to how setuid works.
Traditionally, it has always been possible as root to call


This now fails.  The call to seteuid() succeeds but the the second call
fails leaving the uid=0 and the euid=someid

Is there some logic behind this behavior?