From owner-freebsd-bugs  Mon Jan 15 12:10:05 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA04933
          for bugs-outgoing; Mon, 15 Jan 1996 12:10:05 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id MAA04927
          Mon, 15 Jan 1996 12:10:02 -0800 (PST)
Date: Mon, 15 Jan 1996 12:10:02 -0800 (PST)
Message-Id: <199601152010.MAA04927@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: David Muir Sharnoff <muir@idiom.com>
Subject: Re: Re: bin/945: rcp from 2.0.5 w/Kerberos to 2.1 w/DES doesn't work for root 
Reply-To: David Muir Sharnoff <muir@idiom.com>
Sender: owner-bugs@FreeBSD.ORG
Precedence: bulk

The following reply was made to PR bin/945; it has been noted by GNATS.

From: David Muir Sharnoff <muir@idiom.com>
To: Mark Murray <mark@grondar.za>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: Re: bin/945: rcp from 2.0.5 w/Kerberos to 2.1 w/DES doesn't work for root 
Date: Mon, 15 Jan 1996 12:03:05 -0800

 * 
 * > 	Machine A: running FreeBSD 2.0.5.  Kerberos installed, but
 * > 	not really working properly due to lack of decent instructions
 * > 	at the time it was installed (shortly after the 2.0.5 release)
 * > 
 * > 	Machine B: running FreeBSD 2.1.  DES installed, but not Kerberos.
 * 
 * Under these circumstances expect hangs. If kerberos is installed but 
 * not set up properly, kerberised utilities are most likely looking for
 * a wrong/nonexistant kerberos server.
 * 
 * Please look in the 2.1 handbook (/usr/share/doc/handbook) for up-to-date
 * kerberos instructions.
 * 
 * The fastest way to disable kerberos is to rename the /etc/kerberosIV
 * directory to something else.
 * 
 * Please let us know if this works to this problem report can be closed.
 
 Well, the thing is, the 2.1 system is the first one I've found that
 I cannot rcp to.
 
 I didn't have an /etc/kerberosIV directroy in the first place.
 
 -Dave