From owner-freebsd-questions Tue Nov 26 14:29:34 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA02058 for questions-outgoing; Tue, 26 Nov 1996 14:29:34 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA02013 for ; Tue, 26 Nov 1996 14:29:28 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id MAA13221 for ; Tue, 26 Nov 1996 12:25:19 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA23062; Tue, 26 Nov 1996 21:23:33 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA14829; Tue, 26 Nov 1996 21:23:33 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id UAA13906; Tue, 26 Nov 1996 20:56:18 +0100 (MET) From: J Wunsch Message-Id: <199611261956.UAA13906@uriah.heep.sax.de> Subject: Re: setuid under perl5? To: steve@news.cioe.com (Steve Ames) Date: Tue, 26 Nov 1996 20:56:18 +0100 (MET) Cc: freebsd-questions@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611261611.LAA13111@news.cioe.com> from Steve Ames at "Nov 26, 96 11:11:52 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Steve Ames wrote: > I have a couple of scripts written in perl5 that need to edit some files > that are owned by root. I had intended to just setuid the script and go > with it, but no go. > > I'm using Freebsd 2.1.5 and perl5 compiled straight out of > /usr/ports/lang/perl5 (ports-current). The port is known to be broken, and the maintainer already promised to fix it. Removing support for Posix saved IDs from your config file should work. (That's what the /usr/bin/suidperl does.) The security `fix' for the latest suidperl security problems simply is a no-go for 4.4BSDs. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)