This video discusses two interconnected topics: cryptographic key distribution and user authentication. It delves into the complex issues surrounding key distribution, which involves cryptographic protocol and management considerations, providing viewers with an overview of key management and distribution aspects. Additionally, it explores various authentication functions developed to facilitate network-based user authentication. The video offers an in-depth analysis of Kerberos, one of the earliest and most widely-used key distribution and authentication services, examines key distribution schemes using asymmetric encryption, and discusses X.509 certificates and public-key infrastructure. Finally, it introduces the concept of federated identity management.
**Symmetric Key Distribution Using Symmetric Encryption**
In symmetric encryption, both parties sharing the same key must ensure it is protected from unauthorized access, and frequent key changes are encouraged to mitigate data compromise risks. Key distribution, the method of securely delivering a key to both parties without exposing it to others, is crucial for ensuring a cryptographic system's robustness. To distribute a key between two parties, A and B, options include:
1. A physically delivers a selected key to B.
2. A third party selects and physically delivers the key to A and B.
3. If A and B share a recently used key, one can transmit a new key using the existing key for encryption.
4. A third party C, with encrypted connections to A and B, delivers a key over these links.
Options 1 and 2 involve manual key delivery, suitable for link encryption, but are cumbersome for network-wide end-to-end encryption. Option 3 is viable for link encryption or end-to-end, but if a key is compromised, future keys are also at risk. Option 4 is preferred for end-to-end encryption, utilizing:
- Session keys: Unique keys for a session, destroyed post-session.
- Permanent keys: Long-term keys used to distribute session keys.
Key distribution centers (KDCs) manage session keys and communication permissions, providing one-time keys to authorized systems. Automated distribution allows flexible and dynamic server communications, implemented effectively by Kerberos, as described in more detail later.
**Kerberos**
Kerberos, developed at MIT, addresses user authentication in open distributed environments, enabling secure server access while preventing unauthorized access. Threats include unauthorized workstation use to impersonate users, altered network addresses for requests, and eavesdropping on exchanges. Kerberos mitigates these threats using a central authentication server to verify identities. It uses symmetric encryption without public-key encryption, existing in two versions: the older version 4 and the more secure version 5. A simplified exploration of version 4 explains the core of Kerberos: using DES in a protocol to authenticate users. In basic dialogue, Kerberos helps servers authenticate clients to prevent impersonation by requiring a client-server authentication using encrypted tickets and credentials. A ticket-granting server (TGS) refines the process, allowing users to request service-granting tickets from the TGS to access different services without repeatedly entering passwords, enhancing security by embedding timestamps and lifetimes in tickets, ensuring they are valid only within certain periods.
**Kerberos Realms and Multiple Kerberi**
A Kerberos realm consists of a Kerberos server, clients, and application servers sharing the same database with registered user IDs and hashed passwords. Here, a principal represents a service or user in Kerberos, composed of a service/user name, instance name, and realm name. When different administrative domains constitute separate realms, interrealm authentication allows users from one realm to access services in another, provided Kerberos servers share secret keys. In practice, users request tickets from local TGS for remote TGS to access servers in the desired realm. However, the approach struggles to scale with many realms, requiring numerous secure key exchanges. Version 5 rectifies this with fewer requirements.
**Kerberos Version 5**
Kerberos version 5, described in RFC 4120, improves on version 4 by addressing both environmental and technical limitations. It allows flexible encryption systems beyond DES, accommodates various network types, follows ASN.1 and BER for message structuring, offers explicit start and end times in ticket lifetimes, forwards authentication across clients, and simplifies interrealm authentication. Technically, version 5 eliminates double encryption, replaces PCBC with robust integrity checks, negotiates per-connection session keys, and enhances security measures against password attacks through preauthentication. Its dialogue adds elements for user realm, ticket times, and non-replayable nonce values. In matches, it empowers mutual authentication, supports subkey negotiation, and sequence numbers to defend against replay attacks, making overall protocol communications more secure and adaptable than its predecessor.
0 Comments