From owner-freebsd-hackers Sun Nov 24 16:17:44 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA22053 for hackers-outgoing; Sun, 24 Nov 1996 16:17:44 -0800 (PST) Received: from central.picker.com (central.picker.com [144.54.31.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA22046 for ; Sun, 24 Nov 1996 16:17:30 -0800 (PST) Received: from ct.picker.com by central.picker.com with smtp (Smail3.1.28.1 #3) id m0vRoaD-0004riC; Sun, 24 Nov 96 19:07 EST Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA04784; Sun, 24 Nov 96 19:04:55 EST Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id SAA05733; Sun, 24 Nov 1996 18:37:46 -0500 Message-Id: Date: Sun, 24 Nov 1996 18:37:46 -0500 From: rhh@ct.picker.com (Randall Hopper) To: hackers@freebsd.org Subject: suidperl (v5.003) - Doesn't work, Any Tips? X-Mailer: Mutt 0.52 Mime-Version: 1.0 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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. The last few lines of ktrace output are: 6816 ktrace CALL execve(0xefbfd0b8,0xefbfd518,0xefbfd520) 6816 ktrace NAMI "./mountzip" 6816 ktrace NAMI "/usr/local/bin/suidperl" Thumbing the mail archives did reveal suidperl 4.x in /usr/bin, which works fine. But I'm curious as to why suidperl 5.003 didn't work. Is this a config problem on my system? Or is the port busted. Thanks, Randall