From owner-freebsd-ports Mon Nov 25 02:29:51 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05935 for ports-outgoing; Mon, 25 Nov 1996 02:29:51 -0800 (PST) Received: from grackle.grondar.za (grackle.grondar.za [196.7.18.131]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA05744; Mon, 25 Nov 1996 02:29:13 -0800 (PST) Received: from grackle.grondar.za (localhost.grondar.za [127.0.0.1]) by grackle.grondar.za (8.8.3/8.7.3) with ESMTP id MAA07431; Mon, 25 Nov 1996 12:27:27 +0200 (SAT) Message-Id: <199611251027.MAA07431@grackle.grondar.za> To: J Wunsch cc: ports@freebsd.org, hackers@freebsd.org, rhh@ct.picker.com (Randall Hopper) Subject: Re: suidperl (v5.003) - Doesn't work, Any Tips? Date: Mon, 25 Nov 1996 12:27:26 +0200 From: Mark Murray Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > As Randall Hopper wrote: > > > I have a really simple setuid script that used to work with the perl > > 5.001 port. I recently upgraded to 2.2-ALPHA and the 5.003 port, and it > > stopped working: > > > > #!/usr/local/bin/suidperl -w > > > > $ENV{'PATH'} = '/bin:/usr/bin:/usr/sbin:/sbin'; > > exec( "/sbin/mount /zip" ); > > > > It just dumps out without any errors at all. > > This looks as if somebody stupidly assumed the Perl gods are DingTRT. > They aren't. The entire suidperl patches for BSD they've been > emitting don't work. The only thing that works is dropping support > for Posix saved IDs (which was the source of the known suidperl evil > in the first place), and use a similar configuration as the Perl4 in > the base code uses. /usr/bin/suidperl _does_ work, and it's believed > to not have the recent security hole. The stupid one is me. :-(. I'll fix it tonite. M -- Mark Murray PGP key fingerprint = 80 36 6E 40 83 D6 8A 36 This .sig is umop ap!sdn. BC 06 EA 0E 7A F2 CE CE