Skip Menu |
 

Subject: add krb5_cc_new_unique()
/*
* Generates a new unique ccache of `type` in `id'. The supplied
* `hint' (that can be NULL) is a string that the credential cache
* type can use to base the name of the credential on, this is to make
* its easier for the user to differentiate the credentials.
*
* Returns 0 or an error code.
*/

krb5_error_code
krb5_cc_new_unique(krb5_context context, const char *type,
const char *hint, krb5_ccache *id)
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: [krbdev.mit.edu #3091] add krb5_cc_new_unique()
Date: Wed, 8 Jun 2005 15:03:08 -0400
To: rt@krbdev.mit.edu
RT-Send-Cc:
On Jun 8, 2005, at 14:07, Jeffrey Altman via RT wrote:
Show quoted text
> /*
> * Generates a new unique ccache of `type` in `id'. The supplied
> * `hint' (that can be NULL) is a string that the credential cache
> * type can use to base the name of the credential on, this is to make
> * its easier for the user to differentiate the credentials.
> *
> * Returns 0 or an error code.
> */
>
> krb5_error_code
> krb5_cc_new_unique(krb5_context context, const char *type,
> const char *hint, krb5_ccache *id)

And how is this different from krb5_cc_gen_new, which should also
create a unique credentials cache? Oh, yes, that one requires a ccache
object as input, and this one takes a type name. The name should
should reflect that. The words "new unique" could apply to either
interface.

How about krb5_cc_gen_by_type(_name)?
The name of the function and its behavior were discussed for several
weeks on krbdev@mit.edu. Consensus on the name was reached at that
time and Heimdal has already committed the functionality. How strong is
your objection?
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: [krbdev.mit.edu #3091] add krb5_cc_new_unique()
Date: Wed, 8 Jun 2005 16:12:37 -0400
To: rt@krbdev.mit.edu
RT-Send-Cc:
On Jun 8, 2005, at 16:00, Jeffrey Altman via RT wrote:
Show quoted text
> The name of the function and its behavior were discussed for several
> weeks on krbdev@mit.edu. Consensus on the name was reached at that
> time and Heimdal has already committed the functionality. How strong
> is
> your objection?

The behavior I'm fine with, the name ... well, I'm blanking on the
discussion, and it looks like I didn't participate. Not a strong
objection; sensible naming of functions is already something people
shouldn't be expecting of us. :-) Maybe we can fix that when we design
a Real API.

Ken
From: tlyu@mit.edu
Subject: SVN Commit
* src/lib/krb5/ccache/ccbase.c (krb5int_cc_getops): Internal
function to fetch ops vector given ccache prefix string.
(krb5_cc_new_unique): New function to generate a new unique
ccache of a given type.

* src/include/krb5/krb5.hin: Prototype for krb5_cc_new_unique().

* src/lib/krb5/libkrb5.exports:
* src/lib/krb5_32.def: Add krb5_cc_new_unique().

Commit By: tlyu



Revision: 18857
Changed Files:
U trunk/src/include/krb5/krb5.hin
U trunk/src/lib/krb5/ccache/ccbase.c
U trunk/src/lib/krb5/libkrb5.exports
U trunk/src/lib/krb5_32.def
From: tlyu@mit.edu
Subject: SVN Commit
pull up r18857 from trunk

r18857@cathode-dark-space: tlyu | 2006-11-17 20:53:27 -0500
ticket: 3091
tags: pullup

* src/lib/krb5/ccache/ccbase.c (krb5int_cc_getops): Internal
function to fetch ops vector given ccache prefix string.
(krb5_cc_new_unique): New function to generate a new unique
ccache of a given type.

* src/include/krb5/krb5.hin: Prototype for krb5_cc_new_unique().

* src/lib/krb5/libkrb5.exports:
* src/lib/krb5_32.def: Add krb5_cc_new_unique().



Commit By: tlyu



Revision: 18888
Changed Files:
_U branches/krb5-1-6/
U branches/krb5-1-6/src/include/krb5/krb5.hin
U branches/krb5-1-6/src/lib/krb5/ccache/ccbase.c
U branches/krb5-1-6/src/lib/krb5/libkrb5.exports
U branches/krb5-1-6/src/lib/krb5_32.def