On Thu, Aug 23, 2001 at 07:31:02PM +0000, Jeffrey Altman wrote:
> In article <[EMAIL PROTECTED]>,
> those who know me have no need of my name <[EMAIL PROTECTED]> wrote:
> : <9m31ge$ej9$[EMAIL PROTECTED]> divulged:
> :
> : >Actually, nobody adheres to the standard. Not MIT, not Heimdal, not
> : >Microsoft. The RFC says that the principal name is a ASN.1 GeneralString
> : >which means that all strings other than plain ASCII must be encoded
> : >using ISO-2022 escape sequences.
> :
> : that's what i meant by `the deployed world,' i.e., microsoft chose to make
> : win2k 8bit handling neither what the standard requires (iso-2022) nor what
> : virtually all other kerberos distributions do (raw octet-string, therefore
> : usually an iso-8859 alphabet).
>
> The requirement of the use of ISO-2022 was not well known. Everyone
> thought that an ASN.1 GeneralString was simply an octet string. It was
> only after the release of Windows 2000 that anyone released everyone
> was wrong. When the GeneralString is treated as an octet string the
> Microsoft solution to the internationalization problem makes sense.
> This is especially true since an MIT KDC run in a Latin 1 locale cannot
> communicate with a client in a Latin 2 locale.
>From the KDC's point of view the locale it runs is irrelevant (except
for kadmin.local) -- only the locale of the clients is relevant because
the KDC treats GeneralString as an opaque octet string and only does
strict octet-wise equality comparisons of GeneralString items.
The issue of encodings, right now, is strictly to do with the locale of
the program reading the data from a human, which, for the most part is a
client-only issue (again, but for things like kadmin.local).
Or am I missing something?
> Jeffrey Altman * Sr.Software Designer C-Kermit 8.0 Beta available
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.
