Re: preauth_always option?

[Ken Raeburn <raeburn@MIT.EDU>]

On May 29, 2008, at 14:19, Michael B Allen wrote:
> It had occured to me that the "salt hint" should be dealt with  
> outside the
> get_in_tkt loop. But it's not obvious to me as to how one can  
> retrieve the
> ETYPE_INFO after a successful AS-REQ such that it can be cached in  
> some
> way whether it by in a static variable or a file on the client. I  
> suppose
> there could be a set of krb5_get_init_creds_opt_{get,set}_etype_info
> functions.

I would think you'd want to bury this code in the library, and maybe  
have a flag at the API layer enabling or disabling the use of the  
cached data, but otherwise leave it for the internal implementation,  
which has access to all that info.  Why do you think it should be at a  
higher level?

Ken