[1046] in arla-drinkers
Re: forwarding tokens to other machine
daemon@ATHENA.MIT.EDU (assar@stacken.kth.se)
Wed Aug 4 16:33:15 1999
From owner-arla-drinkers@stacken.kth.se Wed Aug 04 20:33:15 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 8748 invoked from network); 4 Aug 1999 20:33:14 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 4 Aug 1999 20:33:14 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id WAA16187
for arla-drinkers-list; Wed, 4 Aug 1999 22:23:40 +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 WAA16175
for <arla-drinkers@stacken.kth.se>; Wed, 4 Aug 1999 22:22:55 +0200 (MET DST)
Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id WAA66138; Wed, 4 Aug 1999 22:23:51 +0200 (CEST)
From: assar@stacken.kth.se
To: Herbert Huber <Herbert.Huber@lrz-muenchen.de>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: forwarding tokens to other machine
References: <37A84A34.B511D8FD@lrz-muenchen.de>
Mime-Version: 1.0 (generated by tm-edit 7.68)
Content-Type: text/plain; charset=ISO-8859-1
Date: 04 Aug 1999 22:23:48 +0200
In-Reply-To: Herbert Huber's message of "Wed, 04 Aug 1999 16:12:05 +0200"
Message-ID: <5loggnl2gb.fsf@assaris.sics.se>
Lines: 30
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 WAA16175
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Herbert Huber <Herbert.Huber@lrz-muenchen.de> writes:
> 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.
Do you need to be compatible with that program?
> 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.).
Yes, this can be done with the kerberos ticket and then creating a new
ticket from that. The functions in krb4 corresponding to the Transarc
decodeTicket() and encodeTicket() would be decomp_ticket() and
krb_create_ticket().
A program that uses these functions to renew kerberos tickets is
available at <ftp://ftp.pdc.kth.se/home/assar/Public/tfutil.tar.gz>.
You could either just call afslog after having renew the ticket or if
that isn't available any longer, use gettoken beforehand.
/assar
