[16036] in Kerberos_V5_Development
Re: Question about krb5_fcc_(destroy vs. close)
daemon@ATHENA.MIT.EDU (Greg Hudson)
Wed Aug 11 12:37:15 2010
From: Greg Hudson <ghudson@mit.edu>
To: Peter Shoults <peter.shoults@oracle.com>
In-Reply-To: <4C62C5CD.8060800@oracle.com>
Date: Wed, 11 Aug 2010 12:37:05 -0400
Message-ID: <1281544625.8066.773.camel@ray>
Mime-Version: 1.0
Cc: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Wed, 2010-08-11 at 11:46 -0400, Peter Shoults wrote:
> It does not appear that either of these routines do all of this. Destroy
> looks like it clears things out completely, but does not free, close
> looks like it disassociates things, and free, but does not clear things
> out. As a follow on, I am confused why we would have two routines that
> appear to do exactly the same thing.
To draw an analogy, this is the difference between deleting a file and
closing a file handle. krb5_cc_destroy is used by programs like
kdestroy, while krb5_cc_close is used whenever a program loses interest
in a credential cache.
A quick read suggests that you could continue to use a ccache handle
(presumably starting with krb5_cc_initialize) after destroying it, but
I'm not certain of that.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
