1 - 3 - 4 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
version
Click on the red underlined text to get to the source
... Kerberos network authentication system is based. It also specifies
Version 5 of the Kerberos protocol. The motivations, goals,
assumptions, and rationale behind most design decisions are treated
...
... system administrator, or application developer. Higher-level papers
describing Version 5 of the Kerberos system [NT94] and documenting
...
... DS81]. The original
design and implementation of Kerberos Versions 1 through 4 was the
work of two former Project Athena staff members, Steve Miller of
Digital Equipment Corporation and Clifford Neuman (now at the
...
... Kerberos.
Version 5 of the Kerberos protocol (described in this document) has
evolved because of new requirements ...
... evolved because of new requirements and desires for features not
available in Version 4. The design of Version 5 was led by Clifford
Neuman and John Kohl with much input from the community. The
...
... requirements and desires for features not
available in Version 4. The design of Version 5 was led by Clifford
Neuman and John Kohl with much input from the community. The
development of the MIT ...
... effort, the document cites the contribution of the proposer.
Reference implementations of both Version 4 and Version 5 of Kerberos
...
...
Reference implementations of both Version 4 and Version 5 of Kerberos
are publicly available, and commercial implementations have been
...
... are publicly available, and commercial implementations have been
developed and are widely used. Details on the differences between
Versions 4 and 5 can be found in [KNT94].
...
... fields often results in the entire message being discarded without an
error indication. Future versions of this specification will provide
guidelines to ensure that ASN.1 fields can be added without creating
...
... client cannot detect replays, fabrications, or
modifications. A solution to this problem will be included in a
future version of the protocol.
...
... KRB_AP_ERR_MSG_TYPE error. If the key version indicated by the
Ticket in the KRB_AP_REQ is not one the server can use (e.g., it
...
... doesn't have the proper key to decipher the ticket.
The ticket is decrypted using the version of the server's key
specified by the ticket. If the decryption routines detect a
...
... client's timestamp plus one. This is not necessary in
Version 5 because Version 5 messages are formatted in such a way that
it is not possible to create ...
... timestamp plus one. This is not necessary in
Version 5 because Version 5 messages are formatted in such a way that
it is not possible to create the reply by judicious message surgery
...
... secret key. Furthermore, the client's key's expiration date
and the key version number fields are left out since these values are
stored along with the client's database ...
... the application.
The message is first checked by verifying that the protocol version
and type fields match the current version ...
... version
and type fields match the current version and KRB_SAFE, respectively.
A mismatch generates a KRB_AP_ERR ...
... the application.
The message is first checked by verifying that the protocol version
and type fields match the current version ...
... version
and type fields match the current version and KRB_PRIV, respectively.
A mismatch generates a KRB_AP_ERR ...
... error code is reported for use by the
application. The message is verified by checking that the protocol
version and type fields match the current version and KRB_CRED,
...
... version and type fields match the current version and KRB_CRED,
respectively. A mismatch generates a KRB_AP_ERR ...
... ISO-646/ECMA-6
[ISO-646/ECMA-6] International Reference Version (IRV) (a.k.a. U.S.
ASCII), which mostly works.
...
... Although this results in changes to the abstract types from the RFC
1510prop(-> 4120prop) version, the encoding in DER should be unaltered. Historical
...
... the constant integer 5. There is no easy way to make this field
into a useful protocol version number, so its value is fixed.
msg-type
...
... kvno
This field contains the version number of the key under which data
is encrypted. It is only present in messages encrypted ...
...
tkt-vno
This field specifies the version number for the ticket format.
This document describes version number 5.
...
... This field specifies the version number for the ticket format.
This document describes version number 5.
realm
...
... pvno
This field is included in each message, and specifies the protocol
version number. This document specifies protocol version 5.
...
... This field is included in each message, and specifies the protocol
version number. This document specifies protocol version 5.
msg-type
...
...
Note that in KRB_TGS_REQ, the protocol version number appears twice
and two different message types appear: the KRB_TGS ...
... secret key, and the client's
key version number is included in the key version number for the
encrypted data ...
... client's
key version number is included in the key version number for the
encrypted data. For KRB_TGS ...
... session key from the TGT used in the
request. In that case, no version number will be present in the
EncryptedData sequence.
...
... The KRB_AP_REQ message contains the Kerberos protocol version number,
the message type KRB_AP ...
... authenticator-vno
This field specifies the version number for the format of the
authenticator. This document specifies version ...
... version number for the format of the
authenticator. This document specifies version 5.
crealm and cname
...
... The KRB_AP_REP message contains the Kerberos protocol version number,
the message type, and an encrypted ...
... Protocol Version Number ...
...
pvno 5 Current Kerberos protocol version number
...
...
Version 5 of the Kerberos protocol supports a myriad of options.
Among these are multiple encryption ...
... Implementations which are configured in this way can be said to
support Kerberos Version 5 Specification 2 (5.2). Specification 1
(deprecated) may be found in RFC 1510prop(-> 4120prop).
...
... Zhu, L., Jaganathan, K., and S. Hartman, "The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2 ...
... Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2", RFC 4121prop, July 2005. ...