Kerberos and network access security
Windows 2000 now has Kerberos security, and this tip, excerpted from InformIT, will tell you the basics in understanding
Since its inception, classic NT has used a proprietary authentication scheme called NT LAN Manager (NTLM) Challenge-Response. With Windows 2000, Microsoft adopted a public domain authentication scheme called Kerberos. Kerberos was developed at MIT as part of Project Athena. It takes its name from the mythological three-headed hound that guarded the gates of the underworld in Roman mythology. (If you're a humanities scholar making the transition to Information Technology, you may wonder why Project Athena picked a Roman mythic creature rather than the Greek counterpart, Cerberus. I can't help you. Computers and classics just don't mix.)
Windows 2000 uses version 5 of Kerberos as defined by RFC 1510, "The Kerberos Network Authentication Service V5." Many Kerberos implementations also use an API library described in RFC 1964, "The Kerberos Version 5 Generic Security Service Application Programming Interface (GSS-API) Mechanism." Windows 2000 does not use the GSS-API directly. Instead, it uses a similar set of function calls exposed by the Security Support Provider Interface (SSPI).
Because the authentication mechanism is designed to be as transparent as possible, it isn't all that obvious that Kerberos is at work rather than the classic NTLM Challenge-Response. Windows 2000 uses Kerberos in the following circumstances:
- Authenticating users logging on to Windows 2000 domain controllers
- Authenticating users logging on to Windows 2000 servers and workstations that are members of a Windows 2000 domain
- Authenticating users logging on to standalone Windows 2000 servers and workstations
- Authenticating users accessing a Windows 2000 server or workstation from a Windows 9x client configured with the Active Directory add-on
NTLM Challenge-Response authentication is used in the following instances:
- Authenticating users logging on to Windows 2000 servers and workstations that are members of a classic NT domain (or accessing a classic NT domain from a Windows 2000 domain via a trust relationship)
- Authenticating users accessing a Windows 2000 server or workstation from a classic NT server or workstation
- Authenticating users accessing a Windows 2000 server from a standard Windows 9x or 3.1x client
If you find yourself wondering how to verify this, you can enable auditing and examine the logged transactions, because a user logs on both at the console of a member workstation and the console of the server.
To read all of this tip, click over to InformIT. You have to register there, but it's free.
Did you like this tip? If so (or if not) why not let us know? Email to sound off.
This was first published in May 2001