From owner-freebsd-current Fri Nov 7 12:00:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA19640 for current-outgoing; Fri, 7 Nov 1997 12:00:40 -0800 (PST) (envelope-from owner-freebsd-current) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA19630 for ; Fri, 7 Nov 1997 12:00:34 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 5830 invoked from network); 7 Nov 1997 20:00:22 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 7 Nov 1997 20:00:22 -0000 Date: Fri, 7 Nov 1997 15:00:17 -0500 (EST) From: Evan Champion To: freebsd-current@freebsd.org Subject: kerberos Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think that the kerberised rlogin is a little screwed... Here's an error message: rlogin: warning, using standard rlogin: krcmd: Xa L rlogin: can't provide Kerberos auth data: No such file or directory Note the extra garbage after the krcmd:. If the 8-bit chars didn't paste, it is the German 'B' (the one that is pronounced 's'), X, a square, space, L. I would guess that is some sort of stack corruption... I haven't absolutely proven it yet, but I think the Kerberised rsh is corrupting data too on large binary transfers. And I can't reliably krlogin from a 3.0-current server to a 3.0-current server (ie: it works as often as it doesn't). Which bones is being used in 3.0-current? Is there anyone maintaining the 3.0-current distribution? Evan