Network Working Group M. Swift
Request for Comments: 3244 University of Washington
Category: Informational J. Trostle
Cisco Systems
J. Brezak
Microsoft
February 2002
Network Working Group M. Swift
Request for Comments: 3244 University of Washington
Category: Informational J. Trostle
Cisco Systems
J. Brezak
Microsoft
February 2002
Microsoft Windows 2000 Kerberos Change Password and Set Password Protocols
Microsoft Windows 2000 Kerberos更改密码和设置密码协议
Status of this Memo
本备忘录的状况
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This memo specifies Microsoft's Windows 2000 Kerberos change password and set password protocols. The Windows 2000 Kerberos change password protocol interoperates with the original Kerberos change password protocol. Change password is a request reply protocol that includes a KRB_PRIV message that contains the new password for the user.
此备忘录指定Microsoft的Windows 2000 Kerberos更改密码和设置密码协议。Windows 2000 Kerberos更改密码协议与原始Kerberos更改密码协议互操作。更改密码是一种请求-应答协议，它包含一条KRB_PRIV消息，其中包含用户的新密码。
Microsoft's Windows 2000 Kerberos change password protocol interoperates with the original Kerberos change password protocol. Change password is a request reply protocol that includes a KRB_PRIV message that contains the new password for the user. The original change password protocol does not allow an administrator to set a password for a new user. This functionality is useful in some environments, and this proposal extends the change password protocol to allow password setting. The changes are: adding new fields to the request message to indicate the principal which is having its password set, not requiring the initial flag in the service ticket, using a new protocol version number, and adding three new result codes.
Microsoft的Windows 2000 Kerberos更改密码协议与原始Kerberos更改密码协议互操作。更改密码是一种请求-应答协议，它包含一条KRB_PRIV消息，其中包含用户的新密码。原始的更改密码协议不允许管理员为新用户设置密码。此功能在某些环境中很有用，并且此建议扩展了更改密码协议以允许密码设置。更改包括：向请求消息添加新字段以指示正在设置密码的主体，不需要服务票证中的初始标志，使用新的协议版本号，以及添加三个新的结果代码。
The service accepts requests on UDP port 464 and TCP port 464 as well. The protocol consists of a single request message followed by a single reply message. For UDP transport, each message must be fully contained in a single UDP packet.
该服务还接受UDP端口464和TCP端口464上的请求。该协议由一条请求消息和一条回复消息组成。对于UDP传输，每条消息必须完全包含在单个UDP数据包中。
For TCP transport, there is a 4 octet header in network byte order that precedes the message and specifies the length of the message.
对于TCP传输，在消息之前有一个按网络字节顺序排列的4个八位字节头，用于指定消息的长度。
Request Message
请求消息
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| message length | protocol version number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AP_REQ length | AP_REQ data /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ KRB-PRIV message /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| message length | protocol version number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AP_REQ length | AP_REQ data /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ KRB-PRIV message /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
All 16 bit fields are in big-endian order.
所有16位字段均按大端顺序排列。
message length field: contains the number of bytes in the message including this field.
消息长度字段：包含包含此字段的消息中的字节数。
protocol version number: contains the hex constant 0xff80 (big-endian integer).
协议版本号：包含十六进制常量0xff80（大端整数）。
AP-REQ length: length of AP-REQ data, in bytes. If the length is zero, then the last field contains a KRB-ERROR message instead of a KRB-PRIV message.
AP-REQ长度：AP-REQ数据的长度，以字节为单位。如果长度为零，则最后一个字段包含KRB-ERROR消息，而不是KRB-PRIV消息。
AP-REQ data: (see [1]) The AP-REQ message must be for the service principal kadmin/changepw@REALM, where REALM is the REALM of the user who wishes to change/set his password. The authenticator in the AP-REQ must include a subsession key. (NOTE: The subsession key must be pseudo-randomly generated and must never be reused for multiple authenticators.) To enable setting of passwords, it is not required that the initial flag be set in the Kerberos service ticket.
AP-REQ数据：（参见[1]）AP-REQ消息必须针对服务主体kadmin/changepw@REALM，其中REALM是希望更改/设置其密码的用户的领域。AP-REQ中的认证器必须包括一个子会话密钥。（注意：子会话密钥必须是伪随机生成的，并且决不能用于多个身份验证程序。）要启用密码设置，不需要在Kerberos服务票证中设置初始标志。
KRB-PRIV message (see [1]) This user-data field in the KRB-PRIV message is encrypted using the subkey from the authenticator in the AP-REQ data. The usec and seq-number fields of the KRB_PRIV message are present and have the same value as the seq-number field in the
KRB-PRIV消息（参见[1]）KRB-PRIV消息中的此用户数据字段使用AP-REQ数据中认证器的子密钥进行加密。KRB_PRIV消息的usec和seq number字段存在，并且与消息中的seq number字段具有相同的值
authenticator from the AP_REQ message (the seq-number in the authenticator will be present). The server ignores the optional r-address field in the KRB_PRIV message, if it is present.
来自AP_REQ消息的验证器（验证器中的序号将出现）。服务器忽略KRB_PRIV消息中的可选r-address字段（如果存在）。
The user-data component of the message consists of the following ASN.1 structure encoded as an OCTET STRING:
消息的用户数据组件由以下编码为八位字节字符串的ASN.1结构组成：
ChangePasswdData ::= SEQUENCE {
newpasswd[0] OCTET STRING,
targname[1] PrincipalName OPTIONAL,
targrealm[2] Realm OPTIONAL
}
ChangePasswdData ::= SEQUENCE {
newpasswd[0] OCTET STRING,
targname[1] PrincipalName OPTIONAL,
targrealm[2] Realm OPTIONAL
}
The server must verify the AP-REQ message, check whether the client principal in the ticket is authorized to set/change the password (either for that principal, or for the principal in the targname field if present), and decrypt the new password. The server also checks whether the initial flag is required for this request, replying with status 0x0007 if it is not set and should be. An authorization failure is cause to respond with status 0x0005. For forward compatibility, the server should be prepared to ignore fields after targrealm in the structure that it does not understand.
服务器必须验证AP-REQ消息，检查票据中的客户端主体是否有权设置/更改密码（对于该主体，或者对于targname字段中的主体，如果存在），并解密新密码。服务器还检查此请求是否需要初始标志，如果未设置且应该设置，则以状态0x0007进行响应。授权失败导致响应状态为0x0005。为了向前兼容，服务器应该准备忽略它不理解的结构中targrealm之后的字段。
The newpasswd field contains the cleartext password, and the server will apply any local policy checks including password policy checks. The server then generates the appropriate keytypes from the password and stores them in the KDC database. If all goes well, status 0x0000 is returned to the client in the reply message (see below).
newpasswd字段包含明文密码，服务器将应用任何本地策略检查，包括密码策略检查。然后，服务器根据密码生成适当的密钥类型，并将其存储在KDC数据库中。如果一切顺利，状态0x0000将在回复消息中返回给客户端（见下文）。
Reply Message
回复信息
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| message length | protocol version number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AP_REP length | AP-REP data /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ KRB-PRIV message /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| message length | protocol version number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AP_REP length | AP-REP data /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/ KRB-PRIV message /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
All 16 bit fields are in big-endian order.
所有16位字段均按大端顺序排列。
message length field: contains the number of bytes in the message including this field.
消息长度字段：包含包含此字段的消息中的字节数。
protocol version number: contains the hex constant 0x0001 (big-endian integer). (The reply message has the same format as the original change password protocol.)
协议版本号：包含十六进制常量0x0001（大端整数）。（回复消息的格式与原始更改密码协议相同。）
AP-REP length: length of AP-REP data, in bytes. If the length is zero, then the last field contains a KRB-ERROR message instead of a KRB-PRIV message.
AP-REP长度：AP-REP数据的长度，以字节为单位。如果长度为零，则最后一个字段包含KRB-ERROR消息，而不是KRB-PRIV消息。
AP-REP data: the AP-REP is the response to the AP-REQ in the request packet.
AP-REP数据：AP-REP是对请求数据包中AP-REQ的响应。
KRB-PRIV message: This KRB-PRIV message must be encrypted with the subsession key from the authenticator in the AP-REQ data.
KRB-PRIV消息：此KRB-PRIV消息必须使用AP-REQ数据中验证器的子会话密钥进行加密。
The server will respond with a KRB-PRIV message unless it cannot decode the client AP-REQ or KRB-PRIV message, in which case it will respond with a KRB-ERROR message. NOTE: Unlike change password version 1, the KRB-ERROR message will be sent back without any encapsulation.
除非服务器无法解码客户端AP-REQ或KRB-PRV消息，否则服务器将以KRB-PRV消息响应，在这种情况下，服务器将以KRB-ERROR消息响应。注意：与更改密码版本1不同，KRB-ERROR消息将在不进行任何封装的情况下发回。
The user-data component of the KRB-PRIV message, or e-data component of the KRB-ERROR message, consists of the following data.
KRB-PRIV消息的用户数据组件或KRB-ERROR消息的电子数据组件由以下数据组成。
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| result code | result string /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| result code | result string /
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
result code (16 bits) (result codes 0-4 are from the original change password protocol):
结果代码（16位）（结果代码0-4来自原始更改密码协议）：
The result code must have one of the following values (big-endian integer):
结果代码必须具有以下值之一（大端整数）：
KRB5_KPASSWD_SUCCESS 0 request succeeds (This value is not allowed in a KRB-ERROR message)
KRB5_KPASSWD_SUCCESS 0请求成功（KRB错误消息中不允许使用此值）
KRB5_KPASSWD_MALFORMED 1 request fails due to being malformed
KRB5_KPASSWD_格式错误的1请求由于格式错误而失败
KRB5_KPASSWD_HARDERROR 2 request fails due to "hard" error in processing the request (for example, there is a resource or other problem causing the request to fail)
KRB5_KPASSWD_HARDERROR 2请求因处理请求时出现“硬”错误而失败（例如，存在导致请求失败的资源或其他问题）
KRB5_KPASSWD_AUTHERROR 3 request fails due to an error in authentication processing
由于身份验证处理中的错误，KRB5_KPASSWD_AUTHERROR 3请求失败
KRB5_KPASSWD_SOFTERROR 4 request fails due to a "soft" error in processing the request
由于处理请求时出现“软”错误，KRB5_KPASSWD_SOFTERROR 4请求失败
KRB5_KPASSWD_ACCESSDENIED 5 requestor not authorized
KRB5_KPASSWD_访问被拒绝5请求者未授权
KRB5_KPASSWD_BAD_VERSION 6 protocol version unsupported
KRB5_KPASSWD_BAD_版本6不支持协议版本
KRB5_KPASSWD_INITIAL_FLAG_NEEDED 7 initial flag required
KRB5\u KPASSWD\u初始标志\u需要7个初始标志
0xFFFF is returned if the request fails for some other reason. Although only a few non-zero result codes are specified here, the client should accept any non-zero result code as indicating failure.
如果请求因其他原因失败，则返回0xFFFF。虽然这里只指定了一些非零结果代码，但客户端应该接受任何非零结果代码，作为指示失败的代码。
result string:
结果字符串：
This field contains information which might be useful to the user, such as feedback about policy failures. The string is encoded in UTF-8. It may be omitted if the server does not wish to include it. If it is present, the client will display the string to the user.
此字段包含可能对用户有用的信息，例如有关策略失败的反馈。该字符串以UTF-8编码。如果服务器不希望包含它，则可以省略它。如果存在，客户端将向用户显示该字符串。
Password policies should be enforced to make sure that users do not pick passwords (for change password) that are vulnerable to brute force password guessing attacks. An administrator who is authorized to set other principal's passwords is highly trusted and must also carefully protect his/her own credentials.
应强制实施密码策略，以确保用户不会选择易受暴力密码猜测攻击的密码（用于更改密码）。被授权设置其他主体密码的管理员是高度受信任的，并且还必须小心保护自己的凭据。
[1] Kohl, J. and C. Neuman, "The Kerberos Network Authentication Service (V5)", RFC 1510, September 1993.
[1] Kohl，J.和C.Neuman，“Kerberos网络身份验证服务（V5）”，RFC15101993年9月。
Mike Swift University of Washington Seattle, WA
西雅图华盛顿大学迈克斯威夫特
EMail: mikesw@cs.washington.edu
EMail: mikesw@cs.washington.edu
Jonathan Trostle Cisco Systems 170 W. Tasman Dr. San Jose, CA 95134
Jonathan Trostle Cisco Systems 170 W.Tasman博士加利福尼亚州圣何塞95134
EMail: john3725@world.std.com
EMail: john3725@world.std.com
John Brezak Microsoft 1 Microsoft Way Redmond, WA 98052
约翰·布雷扎克，华盛顿州雷德蒙微软1号，邮编：98052
EMail: jbrezak@microsoft.com
EMail: jbrezak@microsoft.com
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。