From 6dea05aa26a8cf73164f68776655143a3252180c Mon Sep 17 00:00:00 2001 From: "Todd C. Miller" Date: Tue, 22 Jan 2002 01:58:42 +0000 Subject: [PATCH] Update for new error messages from set_perms() --- PORTING | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/PORTING b/PORTING index 4c3ecdebd..1d42ebd6b 100644 --- a/PORTING +++ b/PORTING @@ -22,10 +22,10 @@ ulimit(2) or getrlimit(2) can also be used on some OS's. If all else fails you can use the value of NOFILE in . Also, some operating systems have a broken implementation of POSIX -saved IDs. If sudo prints the error message "seteuid(0): Operation -not permitted" this means saved IDs are not implemented properly. -You should run configure with the "--disable-saved-ids" option and -rebuild sudo. +saved IDs. If sudo prints the error message "seteuid(0) failed, +your operating system may have broken POSIX saved ID support" this +means saved IDs are not implemented properly. You should run +configure with the "--disable-saved-ids" option and rebuild sudo. Sudo tries to clear the environment of dangerous environment variables such as LD_* to prevent shared library spoofing. If you are porting -- 2.50.1