From owner-freebsd-current Tue Mar 17 12:23:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26035 for freebsd-current-outgoing; Tue, 17 Mar 1998 12:23:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA26007 for ; Tue, 17 Mar 1998 12:23:06 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 13429 invoked from network); 17 Mar 1998 19:30:11 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 17 Mar 1998 19:30:11 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-031298 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199803171739.MAA21000@rtfm.ziplink.net> Date: Tue, 17 Mar 1998 11:30:10 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Mikhail Teterin Subject: Re: Kerberos and telnet, su, rsh.... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Mar-98 Mikhail Teterin wrote: > 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. You are right, of course. Core dumping is normally a side effect of invalid signal. Invalid signal is one that the program has not notified the kernel what it wants done with it. It is a clear mark on unanticipated error/exception. I douby it is the planned-for reaction to unconfigured Kerberos utility running. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message