Lines Matching refs:Windows

5 @node Windows compatibility, Programming with Kerberos, Kerberos 4 issues, Top
7 @chapter Windows compatibility
9 Microsoft Windows, starting from version 2000 (formerly known as Windows NT 5), implements Kerberos…
11 issues between Heimdal and various Windows versions.
13 The big problem with the Kerberos implementation in Windows
21 * Configuring Windows to use a Heimdal KDC::  
22 * Inter-Realm keys (trust) between Windows and a Heimdal KDC::  
26 * Quirks of Windows 2000 KDC::  
27 * Useful links when reading about the Windows::  
30 …ode Configuring Windows to use a Heimdal KDC, Inter-Realm keys (trust) between Windows and a Heimd…
32 @section Configuring Windows to use a Heimdal KDC
34 …Windows Support Tools, available from either the installation CD-ROM (@file{SUPPORT/TOOLS/SUPPORT.…
83 The Windows machine will now map any user to the corresponding principal,
87 …ealm keys (trust) between Windows and a Heimdal KDC, Create account mappings, Configuring Windows …
89 @section Inter-Realm keys (trust) between Windows and a Heimdal KDC
93 Install Windows, and create a new controller (Active Directory
101 You need to tell Windows on what hosts to find the KDCs for the
102 non-Windows realm with @command{ksetup}, see @xref{Configuring Windows 
108 Then you need to add the inter-realm keys on the Windows KDC@. Start the
114 password. When prompted if this is a non-Windows Kerberos realm, press
128 no encryption type stronger than the one configured on Windows side for this
130 Windows, nor any Kerberos 4 salted hashes, as Windows does not seem to
135 @item Windows 2000: maximum encryption type is DES
136 @item Windows 2003: maximum encryption type is DES
137 @item Windows 2003RC2: maximum encryption type is RC4, relationship defaults to DES
138 @item Windows 2008: maximum encryption type is AES, relationship defaults to RC4
141 For Windows 2003RC2, to change the trust encryption type, you have to use the
142 @command{ktpass}, from the Windows 2003 Resource kit *service pack2*, available
149 For Windows 2008, the same operation can be done with the @command{ksetup}, installed by default.
165 And if needed, to remove unsupported encryptions, such as the following ones for a Windows 2003RC2 …
176 never sent to the non-Windows KDC.
178 …ppings, Encryption types, Inter-Realm keys (trust) between Windows and a Heimdal KDC, Windows comp…
188 non-Windows domain.
195 @node Encryption types, Authorisation data, Create account mappings, Windows compatibility
199 Windows 2000 supports both the standard DES encryptions (@samp{des-cbc-crc} and
207 @node Authorisation data, Quirks of Windows 2000 KDC, Encryption types, Windows compatibility
211 The Windows 2000 KDC also adds extra authorisation data in tickets.
235 @node Quirks of Windows 2000 KDC, Useful links when reading about the Windows, Authorisation data, …
237 @section Quirks of Windows 2000 KDC
239 There are some issues with salts and Windows 2000.  Using an empty salt---which is the only one tha…
243 required.  Microsoft have fixed this issue post Windows 2003.
267 @node Useful links when reading about the Windows,  , Quirks of Windows 2000 KDC, Windows compatibi…
269 @section Useful links when reading about the Windows
282 Kerberos GSS-API (in Windows-eze SSPI), Windows as a client in a
283 non-Windows KDC realm, adding unix clients to a Windows 2000 KDC, and
284 adding cross-realm trust (@pxref{Inter-Realm keys (trust) between Windows
287 @item Windows 2000 Kerberos Authentication:
289 White paper that describes how Kerberos is used in Windows 2000.
295 @c @item Klist for Windows:
297 @c Describes where to get a klist for Windows 2000.
315 @uref{http://www.bindview.com/Support/RAZOR/Utilities/Windows/pwdump2_readme.cfm}