[1028] in arla-drinkers
forwarding tokens to other machine
daemon@ATHENA.MIT.EDU (Herbert Huber)
Thu Jul 29 12:30:16 1999
From owner-arla-drinkers@stacken.kth.se Thu Jul 29 16:30:15 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 3867 invoked from network); 29 Jul 1999 16:30:13 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 29 Jul 1999 16:30:13 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id SAA11760
for arla-drinkers-list; Thu, 29 Jul 1999 18:25:25 +0200 (MET DST)
Received: from mailrelay1.lrz-muenchen.de (mailrelay1.lrz-muenchen.de [129.187.254.101])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id SAA11756;
Thu, 29 Jul 1999 18:25:21 +0200 (MET DST)
Received: from [129.187.12.47] by mailout.lrz-muenchen.de with ESMTP; Thu, 29 Jul 1999 18:25:18 +0200
Message-Id: <37A0806C.4F94ADF2@lrz-muenchen.de>
Date: Thu, 29 Jul 1999 18:25:16 +0200
From: Herbert Huber <Herbert.Huber@lrz-muenchen.de>
Organization: Leibniz-Rechenzentrum der Bayerischen Akademie der Wissenschaften
X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.3 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: assar@stacken.kth.se
CC: arla-drinkers@stacken.kth.se, Helmut.Heller@lrz-muenchen.de
Subject: forwarding tokens to other machine
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Hello Assar,
please excuse the late reply. I have now tested your two
proof-of-concept programs under arla-0.25 with linux-2.2.10 Kernel
running on my Intel machines and it works perfectly - Thanks a lot!
So the free AFS client arla can now also be used in CODINE 4.2.8
clusters where the two binaries GetToken and SetToken are needed for
token forwarding to batch machines. Maybe this fact is also interesting
for other arla users. However it seems that arla´s token structure is
different from the token structure of the original AFS client. As
consequece arla´s tokens cannot be extended, using undocumented function
calls of Transarcs AFS libraries. So for non homogen environments, e. g.
sites using both arla and Transarcs AFS client, this fact produces
problems. Is there a way to use the some token format in arla as in
Transarcs AFS client? How can user tokens be extended without using
Transarcs libraries and without giving any passwords in arla?
/Herbert
