Date: Tue, 17 Mar 1998 12:39:38 -0500 (EST) From: Mikhail Teterin <mi@aldan.algebra.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Kerberos and telnet, su, rsh.... Message-ID: <199803171739.MAA21000@rtfm.ziplink.net> In-Reply-To: <199803141210.OAA13837@greenpeace.grondar.za> from "Mark Murray" at "Mar 14, 98 02:10:20 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Murray once stated: =Mikhail Teterin wrote: => After I rebuilt the world with Kerberos support, things like => su, telnet, rsh stopped working, unless explicitly given the => ``-K'' option. I do not have Kerberos set up yet, but I remember, => that previosly in this cases I was just getting something "remote => side does not support Kerberos" or "not in root acl". Now the => programs hang for a while, then dump core... =Configure properly for Kerberos, or build without Kerberos. I believe this to be an unacceptable explanation of why things _crash_. It is my understanding, that system utilities (as well as all well written programs, actually) shall never crash. Other then due to a hardware error, of course. I can accept, that the policy was changed from "warn but run" to "warn and do not run", but simple "do not run" (or "crash") is not acceptable. Surprisingly, nobody offered a better explanation. I'm afraid, people will install Kerberos on -stable and will rightfully complaint about ``su'' dumping core without saying a word. -mi 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?199803171739.MAA21000>