a question of Kerberos ticket expiration

Ji Li jli at MIT.EDU
Sun Oct 17 11:42:55 EDT 2004


I installed Leash on my Windows XP. An inconvenience is that the tickets expire everytime when I reboot the machine. I actually change the lifetime of a ticket to 365 days (It's my home computer and I only use it to print to athena), but the expiration of the kerberos five ticket is still about one day. Would you please tell me how to prolong its lifetime and make it not expire every time I reboot?

Your help is greatly appreciated.

Ji Li
32 Vassar Street, 32-G806
Cambridge, MA 02139
jli at mit.eduuFrom juanibs at meta4.com Mon Oct 18 11:00:37 2004
Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU
	by pch.mit.edu (8.12.8p2/8.12.8) with ESMTP id i9IF0aZZ021066
	for <krbdev at PCH.mit.edu>; Mon, 18 Oct 2004 11:00:36 -0400 (EDT)
Received: from fw1.meta4.es (fw1.meta4.es [])
	for <krbdev at mit.edu>; Mon, 18 Oct 2004 11:00:34 -0400 (EDT)
Received: from no.name.available by fw1.meta4.es
	ESMTP; Mon, 18 Oct 2004 17:00:31 +0200
Received: from localhost (localhost.localdomain [])
	by correcaminos.meta4.com (Postfix) with ESMTP id 2107A320071
	for <krbdev at mit.edu>; Mon, 18 Oct 2004 17:00:27 +0200 (CEST)
Received: from correcaminos.meta4.com ([])port 10024)
	with ESMTP id 12307-05 for <krbdev at mit.edu>;
	Mon, 18 Oct 2004 17:00:26 +0200 (CEST)
Received: from fw1-dmz.meta4.es (unknown [])
	by correcaminos.meta4.com (Postfix) with ESMTP id ACD77320002
	for <krbdev at mit.edu>; Mon, 18 Oct 2004 17:00:26 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 18 Oct 2004 17:00:26 +0200
Message-ID: <94DEF3858F7AB34EB2EE2A3059A3DFDD110E86 at pumba.meta4.com>
Thread-Topic: Implementation of authentication delegation
Thread-Index: AcS1IzOIBXDQ73NfRQew0TkPsGP3XQ=
From: "Juan Ignacio Banquetero Soto" <juanibs at meta4.com>
To: <krbdev at mit.edu>
X-OriginalArrivalTime: 18 Oct 2004 15:00:27.0162 (UTC)
X-Virus-Scanned: by amavisd-new at meta4.com
X-Scanned-By: MIMEDefang 2.42
X-Mailman-Approved-At: Mon, 18 Oct 2004 14:37:59 -0400
Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1
Subject: Implementation of authentication delegation
X-BeenThere: krbdev at mit.edu
X-Mailman-Version: 2.1
Precedence: list
List-Id: Kerberos Developers Mailing List <krbdev.mit.edu>
List-Help: <mailto:krbdev-request at mit.edu?subject=help>
List-Post: <mailto:krbdev at mit.edu>
List-Subscribe: <https://mailman.mit.edu/mailman/listinfo/krbdev>,
	<mailto:krbdev-request at mit.edu?subject=subscribe>
List-Archive: <http://mailman.mit.edu/pipermail/krbdev>
List-Unsubscribe: <https://mailman.mit.edu/mailman/listinfo/krbdev>,
	<mailto:krbdev-request at mit.edu?subject=unsubscribe>
X-List-Received-Date: Mon, 18 Oct 2004 15:00:37 -0000

I´m a newbie and I´m a bit confused. Since there is a lot of information about authentication delegation general procedure, I can´t see neither a sample in which it's implemented nor an acceptable API documentation. 

I need to make and AP_REQ (krb5_mk_req) for a server "C" from a server "B", on behalf of a client "A". what can I do?. 

Thanks in advance

More information about the krbdev mailing list