[1045] in arla-drinkers
forwarding tokens to other machine
daemon@ATHENA.MIT.EDU (Herbert Huber)
Wed Aug 4 10:21:28 1999
From owner-arla-drinkers@stacken.kth.se Wed Aug 04 14:21:27 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 7054 invoked from network); 4 Aug 1999 14:21:27 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 4 Aug 1999 14:21:27 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id QAA07969
for arla-drinkers-list; Wed, 4 Aug 1999 16:12:12 +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 QAA07965;
Wed, 4 Aug 1999 16:12:07 +0200 (MET DST)
Received: from [129.187.12.47] by mailout.lrz-muenchen.de with ESMTP; Wed, 4 Aug 1999 16:12:05 +0200
Message-Id: <37A84A34.B511D8FD@lrz-muenchen.de>
Date: Wed, 04 Aug 1999 16:12:05 +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
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
In "Transarcs" or "CODINE´s "version of GetToken the following
structures are printed to STDOUT in the following order:
ktc_principal service
ktc_principal client
ktc_token token
Redirecting the output to the local harddisk produces a file with a
length of 752 bytes, whereas your GetToken binary writes only 92 bytes
to STDOUT. The output of Transarcs GetToken is the same, using
arla or the original AFS client. So you are right, there seems to be no
difference in the token structure.
By extend I wanted to say extending the lifetime of the token. This can
be done by having the secret key of the server available, decoding the
AFS token and fabricate a new token, using the information of the old
token (AFS ID, etc.).
/Herbert
