Received: from konishi-polis.mit.edu (HOTASS-9.MIT.EDU [18.101.1.46]) by krbdev.mit.edu (8.9.3p2) with ESMTP id QAA11287; Tue, 6 Jan 2004 16:14:26 -0500 (EST)
Received: by konishi-polis.mit.edu (Postfix, from userid 8042) id B1D3A1515EA; Tue,  6 Jan 2004 16:14:23 -0500 (EST)
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #2106] bug in krb5_cc_remove_cred API?
References: <rt-2106-9067.0.362638267497033@krbdev.mit.edu> <Pine.GSO.4.58.0401061547040.29313@galaxy.argfrp.us.uu.net>
From: Sam Hartman <hartmans@mit.edu>
Date: Tue, 06 Jan 2004 16:14:23 -0500
In-Reply-To: <Pine.GSO.4.58.0401061547040.29313@galaxy.argfrp.us.uu.net> (gsu@UU.NET's message of "Tue, 6 Jan 2004 15:58:55 -0500 (EST)")
Message-Id: <tslhdz8dbkg.fsf@konishi-polis.mit.edu>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
RT-Send-Cc: 
X-RT-Original-Encoding: us-ascii
Content-Length: 715

>>>>> "gsu" == gsu  <gsu@UU.NET> writes:

    gsu> Returning an error would certainly be much cleaner than a
    gsu> null pointer reference.  I was so puzzled that I checked the
    gsu> API guide and my code repeatly.  If no implementation is
    gsu> intended, why advertise it in the guide?

An implementation is intended.  The API guide in doc/api does not
particularly correspond to the source code.  We do not really have API
documentation to speak of at this time.

    gsu> So there is no way that I can remove any expired credential?

Correct, but it is probably not a major problem; expired credentials
will not be used.  If your cache is getting too full, remove all the
credentials and get a new TGT.