[krbdev.mit.edu #3091] add krb5_cc_new_unique()

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[krbdev.mit.edu #3091] add krb5_cc_new_unique()

Greg Hudson via RT
/*
 * 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)
_______________________________________________
krb5-bugs mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
Reply | Threaded
Open this post in threaded view
|

Re: [krbdev.mit.edu #3091] add krb5_cc_new_unique()

Greg Hudson via RT
On Jun 8, 2005, at 14:07, Jeffrey Altman via RT wrote:

> /*
>  * 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)?


_______________________________________________
krb5-bugs mailing list
[hidden email]
https://mailman.mit.edu/mailman/listinfo/krb5-bugs