[1035] in arla-drinkers
Re: "tokens" script unusable
daemon@ATHENA.MIT.EDU (Love)
Fri Jul 30 15:36:41 1999
From owner-arla-drinkers@stacken.kth.se Fri Jul 30 19:36:40 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 8620 invoked from network); 30 Jul 1999 19:36:40 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 30 Jul 1999 19:36:40 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id VAA18162
for arla-drinkers-list; Fri, 30 Jul 1999 21:32:14 +0200 (MET DST)
Received: from elixir.e.kth.se (elixir.e.kth.se [130.237.48.5])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id VAA18158
for <arla-drinkers@stacken.kth.se>; Fri, 30 Jul 1999 21:32:10 +0200 (MET DST)
Received: from hummel.e.kth.se (hummel.e.kth.se [130.237.43.135])
by elixir.e.kth.se (8.9.3/8.9.3) with ESMTP id VAA17193;
Fri, 30 Jul 1999 21:32:08 +0200 (MET DST)
Received: (from lha@localhost)
by hummel.e.kth.se (8.9.3/8.9.3) id VAA16668;
Fri, 30 Jul 1999 21:32:06 +0200 (MET DST)
From: Love <lha@stacken.kth.se>
To: uri@watson.ibm.com
Cc: arla-drinkers@stacken.kth.se
Subject: Re: "tokens" script unusable
References: <9907301923.AA29490@buoy.watson.ibm.com>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: 30 Jul 1999 21:32:05 +0200
In-Reply-To: uri's message of Fri, 30 Jul 1999 15:23:46 -0400 (EDT)
Message-ID: <amemhqj5my.fsf@hummel.e.kth.se>
Lines: 22
X-Mailer: Gnus v5.5/Emacs 20.2
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
uri <uri@watson.ibm.com> writes:
> "tokens" script that comes with arla, sems to be 100% unusable.
> Because it relies on non-kerberos option "-tokens" which no
> standard "klist" recognizes.
There is a tokens by Chris Wing in next release.
> Please, don't make arla a part of kth-krb kit.
We try to not.
For us there exist *NOTHING* else except kth-krb and heimdal.
If you find kth-krb related bugs, tell us and/or send patches, and please
understand our reluctancy in implementing functionallty that we have in
other stuff like kth-krb.
Eventionally we'll get around fixing it for you. Don't hold you breath.
Love
