[1057] in arla-drinkers
Re: forwarding tokens to other machine
daemon@ATHENA.MIT.EDU (Dr A V Le Blanc)
Thu Aug 5 09:20:04 1999
From owner-arla-drinkers@stacken.kth.se Thu Aug 05 13:20:03 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 11745 invoked from network); 5 Aug 1999 13:20:02 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 5 Aug 1999 13:20:02 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id PAA07355
for arla-drinkers-list; Thu, 5 Aug 1999 15:13:49 +0200 (MET DST)
Received: from serenity.mcc.ac.uk (serenity.mcc.ac.uk [130.88.200.93])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id PAA07347
for <arla-drinkers@stacken.kth.se>; Thu, 5 Aug 1999 15:13:04 +0200 (MET DST)
Received: from meissen.mcc.ac.uk ([130.88.203.42])
by serenity.mcc.ac.uk with esmtp (Exim 1.92 #3)
for arla-drinkers@stacken.kth.se
id 11CNKS-000M2R-00; Thu, 5 Aug 1999 14:13:04 +0100
Received: (from zlsiial@localhost)
by meissen.mcc.ac.uk (8.7.6/8.8.4)
id OAA25503 for arla-drinkers@stacken.kth.se; Thu, 5 Aug 1999 14:13:03 +0100 (BST)
Message-ID: <19990805141303.A25493@afs.mcc.ac.uk>
Date: Thu, 5 Aug 1999 14:13:03 +0100
From: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
To: arla-drinkers@stacken.kth.se
Subject: Re: forwarding tokens to other machine
Reply-To: Dr A V Le Blanc <LeBlanc@mcc.ac.uk>
References: <37A84A34.B511D8FD@lrz-muenchen.de> <5loggnl2gb.fsf@assaris.sics.se> <37A938B5.D7DB12E8@lrz-muenchen.de> <19990805100426.B25395@afs.mcc.ac.uk> <5lk8raa5wg.fsf@assaris.sics.se> <19990805134224.A25471@afs.mcc.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.1i
In-Reply-To: <19990805134224.A25471@afs.mcc.ac.uk>; from Dr A V Le Blanc on Thu, Aug 05, 1999 at 01:42:24PM +0100
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
I should make clear, if I haven't already that I have experimented
with tokens generated on machine A, transferred to machine B using
AFS-ised ssh 1.2.26 with KTH Kerberos-4 (in various versions);
note that in each case the token is valid on machine A:
Token from A Send to B Result:
arla 0.26 arla 0.26 token works on B
arla 0.26 AFS 3.4a tokens works on B
arla 0.26 AFS 3.5 token is invalid on B
AFS 3.4a arla 0.26 token works on B
AFS 3.4a AFS 3.4a token works on B
AFS 3.4a AFS 3.5 token works on B
AFS 3.5 arla 0.26 token works on B
AFS 3.5 AFS 3.4a token works on B
AFS 3.5 AFS 3.5 token works on B
So, as far as I can see, something about the arla-generated token
is unacceptable to Transarc's AFS 3.5. The arla machines are all
running Linux 2.2.10 with arla 0.26 and kth-krb 19990508 snapshot.
The 3.4a AFS machines are running a number of operating systems,
including Irix 6.5. The 3.5 AFS machines are running Irix 6.5.
-- Owen
LeBlanc@mcc.ac.uk
