From owner-freebsd-current  Tue Mar 17 09:39:50 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA04159
          for freebsd-current-outgoing; Tue, 17 Mar 1998 09:39:50 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04140
          for <freebsd-current@freebsd.org>; Tue, 17 Mar 1998 09:39:46 -0800 (PST)
          (envelope-from mi@rtfm.ziplink.net)
Received: from rtfm.ziplink.net (rtfm [199.232.255.52])
	by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id RAA03155
	for <freebsd-current@freebsd.org>; Tue, 17 Mar 1998 17:39:39 GMT
	(envelope-from mi@rtfm.ziplink.net)
Received: (from mi@localhost)
	by rtfm.ziplink.net (8.8.8/8.8.5) id MAA21000
	for freebsd-current@freebsd.org; Tue, 17 Mar 1998 12:39:39 -0500 (EST)
From: Mikhail Teterin <mi@aldan.algebra.com>
Message-Id: <199803171739.MAA21000@rtfm.ziplink.net>
Subject: Re: Kerberos and telnet, su, rsh....
In-Reply-To: <199803141210.OAA13837@greenpeace.grondar.za> from "Mark Murray" at "Mar 14, 98 02:10:20 pm"
To: freebsd-current@FreeBSD.ORG
Date: Tue, 17 Mar 1998 12:39:38 -0500 (EST)
X-Face: 
	%UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
		 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
		 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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