Date: Wed, 05 Feb 2003 16:23:54 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Mike Makonnen <mtm@identd.net> Cc: "Jacques A. Vidrine" <nectar@FreeBSD.org>, anoop@ranganath.com, freebsd-current@FreeBSD.org Subject: Re: tmpfile breakage on setuid executables Message-ID: <3E41AB1A.691993E8@mindspring.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E41AB1A.691993E8>