Extending rd_req() to handle tkt authz/ext data?

[Nicolas Williams]

The MIT krb5 ought to have an API for enumerating and accessing the
authorization data elements in the ticket of an AP-REQ being accepted.

Similarly with ticket extensions (though that won't be applicable until
Purple comes along the API probably ought to be designed now).

In fact, all typed holes should be coupled with an API for getting at
them where that's applicable. Me-thinks.

The more interesting question is how to represent these things to apps.

Here the fact that DER and explicit tagging are used could work in the
favor of the API designer. I.e., for unknown authz/extension data types
provide the app with a type/value interface to such things and include
type names where they are known, but also the type integer and tags as
they appear. For known authz/extension data types more comfortable
structures could be defined.

Cheers,

Nico
-- 

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.