Unicode and APIs

Jeffrey Altman jaltman at secure-endpoints.com
Wed Sep 19 17:57:00 EDT 2007

Sam Hartman wrote:

> You probably want to assume ticket caches are in some consistent
> locale across the system.
> If you receieve a new ticket as a service you need to know what
> charset to convert it to.

What do you do with tickets whose principal names can be represented in
UNICODE but not in the locale charset?  The application if it has set
the UTF8 flag will be able to process the ticket but won't be able to
cache it.

Hmm.  Perhaps what you do is attempt to translate it to the locale
charset and if that fails, you preface the UTF8 string with an encoding
marker and then store it that way.  The apps that are not setting the
UTF8 flag (or are using non-UNICODE aware krb5 libraries) will not be
able to match the entry.  Any string that is stored without the marker
is treated as the locale charset.

Jeffrey Altman

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3355 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mailman.mit.edu/pipermail/krbdev/attachments/20070919/b9f525b7/attachment.bin

More information about the krbdev mailing list