@c $Id$
+
@node Windows compatibility, Programming with Kerberos, Kerberos 4 issues, Top
@comment node-name, next, previous, up
@chapter Windows compatibility
* Encryption types::
* Authorisation data::
* Quirks of Windows 2000 KDC::
-* Useful links when reading about the Windows 2000::
+* Useful links when reading about the Windows::
@end menu
-@node Configuring Windows to use a Heimdal KDC, Inter-Realm keys (trust) between Windows and a Heimdal KDC, Windows compatability, Windows compatability
+@node Configuring Windows to use a Heimdal KDC, Inter-Realm keys (trust) between Windows and a Heimdal KDC, Windows compatibility, Windows compatibility
@comment node-name, next, precious, up
@section Configuring Windows to use a Heimdal KDC
for example @samp{nisse} to the principal @samp{nisse@@MY.REALM}.
(This is most likely what you want.)
-@node Inter-Realm keys (trust) between Windows and a Heimdal KDC, Create account mappings, Configuring Windows to use a Heimdal KDC, Windows compatability
+@node Inter-Realm keys (trust) between Windows and a Heimdal KDC, Create account mappings, Configuring Windows to use a Heimdal KDC, Windows compatibility
@comment node-name, next, precious, up
@section Inter-Realm keys (trust) between Windows and a Heimdal KDC
running @command{ksetup}). It looks like it might work, but packets are
never sent to the non-Windows KDC.
-@node Create account mappings, Encryption types, Inter-Realm keys (trust) between Windows and a Heimdal KDC, Windows compatability
+@node Create account mappings, Encryption types, Inter-Realm keys (trust) between Windows and a Heimdal KDC, Windows compatibility
@comment node-name, next, precious, up
@section Create account mappings
the Active Directory LDAP catalog. When you create users by script you
can add this entry instead.
-@node Encryption types, Authorisation data, Create account mappings, Windows 2000 compatability
+@node Encryption types, Authorisation data, Create account mappings, Windows compatibility
@comment node-name, next, previous, up
@section Encryption types
only have MD4 passwords and will need a password change to get a DES
key.
-@node Authorisation data, Quirks of Windows 2000 KDC, Encryption types, Windows 2000 compatability
+@node Authorisation data, Quirks of Windows 2000 KDC, Encryption types, Windows compatibility
@comment node-name, next, previous, up
@section Authorisation data
analysing the data.
@end enumerate
-@node Quirks of Windows 2000 KDC, Useful links when reading about the Windows 2000, Authorisation data, Windows 2000 compatability
+@node Quirks of Windows 2000 KDC, Useful links when reading about the Windows, Authorisation data, Windows compatibility
@comment node-name, next, previous, up
@section Quirks of Windows 2000 KDC
These configuration options will make sure that no checksums of the
unsupported types are generated.
-@node Useful links when reading about the Windows 2000, , Quirks of Windows 2000 KDC, Windows compatability
+@node Useful links when reading about the Windows, , Quirks of Windows 2000 KDC, Windows compatibility
@comment node-name, next, previous, up
-@section Useful links when reading about the Windows 2000
+@section Useful links when reading about the Windows
See also our paper presented at the 2001 Usenix Annual Technical
Conference, available in the proceedings or at
@uref{http://www.microsoft.com/technet/prodtechnol/windows2000serv/howto/kerbstep.mspx}.
Kerberos GSS-API (in Windows-eze SSPI), Windows as a client in a
non-Windows KDC realm, adding unix clients to a Windows 2000 KDC, and
-adding cross-realm trust (@pxref{Inter-Realm keys (trust) between Windows 2000
+adding cross-realm trust (@pxref{Inter-Realm keys (trust) between Windows
and a Heimdal KDC}).
@item Windows 2000 Kerberos Authentication: