Password 

Changing
The current status of password-changing rules of conduct in Kerberos 5 is just like that of
Kerberos 4; unfortunately, as in Kerberos 4, password changing has been treated as
an little thought after an event. The original Kerberos 5 (detailed descriptions of exactly what is
required), as defined by RFC 1510, do
not define a way clients can change their own passwords. Older putting into uses
of MIT Kerberos 5 used the (related to managing and running a company or organization) rules of
conduct to perform password
changes, but this is not (able to work with each other) between putting into uses as every
putting into use uses a different (related to managing and running a company or organization) rules of
conduct. A standard rules of conduct for
Kerberos 5 password changing was proposed as an Internet draft in 1998, referred to
as the Horowitz password-changing rules of conduct. The newer versions of MIT (1.2 and
above) and Heimdal Kerberos, as well as the Windows 2000 and 2003 based Active
Directory, support the Horowitz password-changing rules of conduct. Other putting into uses,
such as Solaris' SEAM, do not support this rules of conduct and therefore are not
(able to work with each other) with any other putting into use for password changes.
A new draft proposal is now being discussed to replace the Horowitz passwordchanging
rules of conduct. This proposal, the Kerberos Set/Change Password Version 2, is
the current Internet Draft proposal for Kerberos password changing. This new proposal
has (more than two, but not a lot of) advantages over the Horowitz password-changing rules of
conduct. First, it
provides the ability for managers to reset other users' passwords, as well as
allowing users to change their own passwords.