[1038] in arla-drinkers
Re: forwarding tokens to other machine
daemon@ATHENA.MIT.EDU (assar@stacken.kth.se)
Sat Jul 31 00:46:44 1999
From owner-arla-drinkers@stacken.kth.se Sat Jul 31 04:46:43 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 10057 invoked from network); 31 Jul 1999 04:46:42 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 31 Jul 1999 04:46:41 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id GAA29648
for arla-drinkers-list; Sat, 31 Jul 1999 06:41:54 +0200 (MET DST)
Received: from assaris.sics.se (assaris.sics.se [193.10.66.108])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id GAA29644
for <arla-drinkers@stacken.kth.se>; Sat, 31 Jul 1999 06:41:48 +0200 (MET DST)
Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id GAA55315; Sat, 31 Jul 1999 06:42:32 +0200 (CEST)
From: assar@stacken.kth.se
To: Herbert Huber <Herbert.Huber@lrz-muenchen.de>
Cc: arla-drinkers@stacken.kth.se, Helmut.Heller@lrz-muenchen.de
Subject: Re: forwarding tokens to other machine
References: <37A0806C.4F94ADF2@lrz-muenchen.de>
Mime-Version: 1.0 (generated by tm-edit 7.68)
Content-Type: text/plain; charset=ISO-8859-1
Date: 31 Jul 1999 06:42:27 +0200
In-Reply-To: Herbert Huber's message of "Thu, 29 Jul 1999 18:25:16 +0200"
Message-ID: <5ln1wdmnv0.fsf@assaris.sics.se>
Lines: 26
X-Mailer: Gnus v5.5/Emacs 19.34
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by sundance.stacken.kth.se id GAA29644
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Herbert Huber <Herbert.Huber@lrz-muenchen.de> writes:
> However it seems that arla´s token structure is different from the
> token structure of the original AFS client.
Hm, as far as I know there should be nothing different in the
structure of the tokens. Can you tell me exactly what's different?
> As consequece arla´s tokens cannot be extended, using undocumented
> function calls of Transarcs AFS libraries.
By extend here, do you mean as in adding other information or for
extending the lifetime of a current token? I guess the second one.
What undocumented functions in the Transarc libraries did you use for
this?
> How can user tokens be extended without using Transarcs libraries
> and without giving any passwords in arla?
I'm curious as to how tokens can be extended with Transarc libraries?
To many understanding the only way of extending a token is to have the
secret key of the client or the server and actually fabricate a new
token (ticket really). This can of course be done in several
different ways.
/assar
