Date: Wed, 05 Jun 1996 19:16:34 EST From: "Kaleb S. KEITHLEY" <kaleb@x.org> To: Gary Jennejohn <Gary.Jennejohn@munich.netsurf.de> Cc: hackers@freefall.FreeBSD.org Subject: Re: /dev/tty and nits in 2.2-960501-SNAP Message-ID: <199606052316.TAA10572@exalt.x.org> In-Reply-To: Your message of Wed, 05 Jun 1996 23:12:44 EST. <199606052312.XAA13547@peedub.gj.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> > Throwing caution to the wind I've just overwritten my 2.1R system > >> > with the 2.2-960501-SNAP. > >> > > >> > Things I note thus far: > >> > > >> > # ls -l /dev/tty > >> > crw-r--r-- 1 root wheel 1, 0 5 Jun 10:16 /dev/tty > >> > > >> > really wants to be: > >> > > >> > crw-rw-rw- 1 root wheel 1, 0 5 Jun 10:16 /dev/tty > >> > > >> > otherwise xterm cannot open it. Breaking xterm is a Bad Thing (tm). > > xterm is supposed to be suid root so that can make a utmp entry. At least, > it is on all the systems I have access to. Installed is one thing. :-) I never install, so my xterms are never suid root. My "installed" xterm is just a symlink back into my build tree. I don't care about utmp entries, but that's just me. Some sites specifically don't install xterm suid root because it's a security hole. xterm should work whether it's suid root or not. It did in 2.1. Andrey points out that the permissions in the tar file are wrong. If I remake them with MAKEDEV they have the "correct" permissions. And for what it's worth (probably not much) xterm works (suid root and otherwise) on every system I have access to, and that's quite a few. If FreeBSD wants to break xterm, I think that would be a Bad Thing. -- Kaleb KEITHLEY X Consortium ------- End of Unsent Draft
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606052316.TAA10572>