krb5_cc_gen_new

[Alexandra Ellwood]

Oops, I apparently wasn't paying attention.  Ignore me.  :-)


On Jan 5, 2005, at 4:25 AM, Love wrote:



>
> Alexandra Ellwood <lxs at mit.edu> writes:
>
>
>> I have no objections to the hint parameter so long as it is
>> optional. I've been wanting a useful krb5_cc_*() API to create
>> temporary ccaches for a while.
>>
>> One thing that I would like to suggest is that the function take
>> separate type and name arguments for the hint.
>>
>
> This was the proposed function prototype:
>
> /*
>  * 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)
>
> I think that agrees with you text above, just to make sure, with the
> exception of that `type' can be NULL, but that is easy enough to fix.
>
>
>> Note that making the name hint work with the CCAPI is going to be a
>> pain in the butt. The CCAPI only provides a "create new unique ccache"
>>
>
> And yes, in the initial version, Heimdal will ignore the hint until we 
> have
> hidden the content of krb5_cc_ops structure.
>
> Love
>
>