From owner-freebsd-current Sun Nov 16 20:32:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA10002 for current-outgoing; Sun, 16 Nov 1997 20:32:53 -0800 (PST) (envelope-from owner-freebsd-current) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id UAA09993 for ; Sun, 16 Nov 1997 20:32:47 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 10735 invoked from network); 17 Nov 1997 04:32:40 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 17 Nov 1997 04:32:40 -0000 Date: Sun, 16 Nov 1997 23:32:39 -0500 (EST) From: Evan Champion To: Brian Somers , markm@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: Which setuid's don't work? In-Reply-To: <199711162228.WAA01654@awfulhak.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 16 Nov 1997, Brian Somers wrote: > Works fine. Ppp used to use setreuid() and now uses seteuid(). I tried a few different applications this afternoon, including perl5, and removed any hope of them using anything but seteuid() and they all worked just fine. To Mark, I think it would be appropriate to set the perl5 hints for 3.0 as follows: # # Guesses at what will be needed after 2.2 *) useshrplib='true' so='so' dlext='so' usevfork='true' usemymalloc='n' d_dosuid='define' ;; esac I turned on useshrplib because it doesn't seem useful to me to statically link against libperl if you're going to use a shared libc and co... It might also be nice if a link is made from the libperl.so.4.4 in the depths of /usr/local/lib/perl5 to /usr/local/lib/libperl.so.4.4. That will make it easier for folks doing embedded perl. (I'd also be inclined to set privlib=/usr/local/libdata/perl5, but I think the above should be good for the average user, and the purists (myself included) can use libdata :-) Evan