From owner-freebsd-current Wed Feb 5 16:27:59 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46A1B37B401; Wed, 5 Feb 2003 16:27:58 -0800 (PST) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CDC943F75; Wed, 5 Feb 2003 16:27:57 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0205.cvx21-bradley.dialup.earthlink.net ([209.179.192.205] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 18gZtU-0007RP-00; Wed, 05 Feb 2003 16:27:57 -0800 Message-ID: <3E41AB1A.691993E8@mindspring.com> Date: Wed, 05 Feb 2003 16:23:54 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Makonnen Cc: "Jacques A. Vidrine" , anoop@ranganath.com, freebsd-current@FreeBSD.org Subject: Re: tmpfile breakage on setuid executables References: <00e201c2cd5b$14f31c30$0c02040a@ranganath> <3E41846A.39AAE406@mindspring.com> <015c01c2cd60$7b6dc0a0$0c02040a@ranganath> <3E418C3C.F4B99C78@mindspring.com> <3E419743.6144BE0B@mindspring.com> <20030205232854.GC86606@opus.celabo.org> <20030205235146.ELJQ10203.pop017.verizon.net@kokeb.ambesa.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4f2cfbe19181eaa80a3732a4ca25bead72601a10902912494350badd9bab72f9c350badd9bab72f9c Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Makonnen wrote: > The original poster was right. > The following patch should fix it. I'll check it in as soon as my test cycle is > over. Holy heck. Good freaking catch! I would never have thought of looking for zebras, since it worked on my 5.0 system, with all my test programs. I thought of all *sorts* of crap, but not zebras: o Wrong permissions on /tmp o Wrong permissions on /tmp's mount point o TMPDIR being set to some place strange, like an SMBFS mount o "nosuid" on the mount of the FS where he was running the program in question o Someone "making /tmp more secure" by removing group permissions, and the user in question being in the (now) exclusion group o Etc.. -- Terry "killed by a zebra while wearing a pointy hat" Lambert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message