Expand description
§Kerberos Version 5
This is an implementation of the data types from RFC 4120 also known as “Kerberos V5”. Kerberos is an authentication framework for verifying identities of “principals” (e.g. a user or network server) on an open unprotected network.
This is accomplished without relying on assertions by the host operating system, without basing trust on host addresses, without requiring physical security of all the hosts on the network, and under the assumption that packets traveling along the network can be read, modified, and inserted at will. Kerberos performs authentication under these conditions as a trusted third-party authentication service by using conventional (shared secret key) cryptography.
Like other rasn
core crates this crate does not provide the ability to
authenticate on its own, but provides shared data types to create your own
Kerberos clients and servers.
Modules§
- One-Time Password Pre-authentication
Structs§
- Used to implement an “or” operation by setting the condition-count field to
1
, and it may specify an “and” operation by setting the condition count to the number of embedded elements. - Provides a means for Kerberos principal credentials to embed within themselves privilege attributes and other mechanisms for positive authorization.
- Options for ApReq.
- The initial KDC response.
- Initial ticket request.
- The authenticator included in the ApReq.
- Checksum of cleartext data.
- The body of ApRep.
- The encrypted initial request.
- The encrypted part of the KdcRep body.
- The body of KrbCred.
- The body of KrbPriv.
- The encrypted subsequent request.
- The encrypted part of a Ticket.
- Container for arbitrary encrypted data
- The means by which cryptographic keys used for encryption are transferred.
- The address of a given host.
- The main KDC body.
- The ticket request struct.
- The remaining fields in ticket request. If a checksum is generated for the request, it is done using this field.
- Message that can be used to send Kerberos credentials from one principal to another.
- The tickets and information needed to use them in KrbCred.
- An error from Kerberos.
- Message containing user data along with a collision-proof checksum keyed with the last encryption key negotiated via subkeys, or with the session key if no negotiation has occurred.
- The body of KrbSafe.
- The time of the last request.
- Pre-Authenication data.
- The name of the party to verify. Taken together, a PrincipalName and a Realm form a principal identifier.
- Subsequent KDC response.
- Additional ticket request.
- Record that helps a client authenticate to a service.
- Various options that were used or requested when the ticket was issued.
Enums§
Constants§
Type Aliases§
- Element are intended for interpretation only by application servers that understand the particular
type
of the embedded element. - Authorization data.
- The name of the authentication server.