From owner-freebsd-current  Sun Oct 17  9:26:54 1999
Delivered-To: freebsd-current@freebsd.org
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by hub.freebsd.org (Postfix) with ESMTP id 83F4F14A13
	for <freebsd-current@freebsd.org>; Sun, 17 Oct 1999 09:26:51 -0700 (PDT)
	(envelope-from randy@psg.com)
Received: from randy by rip.psg.com with local (Exim 3.03 #1)
	id 11ct91-0005jp-00
	for freebsd-current@freebsd.org; Sun, 17 Oct 1999 09:26:51 -0700
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: FreeBSD Current <freebsd-current@freebsd.org>
Subject: k4 in current
Message-Id: <E11ct91-0005jp-00@rip.psg.com>
Date: Sun, 17 Oct 1999 09:26:51 -0700
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

anyone out there using kerberos4 in current?  i am not succeeding in a mixed
current/stable/bsdi/... environment.

  o the current systen is the keyserver
  o anyone of the systems can get a tgt
  o given a tgt, the stable/bsdi systems can all rlogin/rsh to eachother
    just fine
  o a user on the current system rlogging in to a stable or bsdi system
    succeeds with the rlogin, but typing produces garbage, e.g. here is an
    "ls<eol>"
	test.psg.com:/usr/randy> \303t
  o a bsdi or stable system can not rlogin/rsh into the current system
        psg.com:/usr/home/randy> rlogin -x rip
	rlogin: krcmd_mutual: Generic kerberos error (kfailure)
	rlogin: the -x flag requires Kerberos authentication
    and the syslog on the current/server system shows
        Oct 17 09:24:49 rlogind[21997]: usage: rlogind [-Dalnx]
	Oct 17 09:24:49 rlogind[21997]: Connection from 147.28.0.62 \
	                                on illegal port

randy


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message