1 / 7

A Private Key System

A Private Key System. KERBEROS. User (U). Kerberos Server (K). Ticket Granting Server (tgs). Client (C). user secret key database. server secret key database. Server. Kerberos: Structure. Requirements: each user has a private password known only to the user

art
Download Presentation

A Private Key System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Private Key System KERBEROS CS5204 – Operating Systems

  2. User (U) Kerberos Server (K) Ticket Granting Server (tgs) Client (C) user secret key database server secret key database Server Kerberos: Structure • Requirements: • each user has a private password known only to the user • a user’s secret key can be computed by a one-way function from the user’s password • the Kerberos server knows the secret key of each user and the tgs • each server has a secret key know by itself and tgs CS 5204 – Operating Systems

  3. User (U) Kerberos Server (K) Ticket Granting Server (tgs) Client (C) user secret key database server secret key database Server Kerberos: Steps authentication authorization CS 5204 – Operating Systems

  4. Kerberos Server (K) Ticket Granting Server (tgs) Server Protocol Overview 2. Tu,tgs User (U) 3. (Tu,tgs, S) Client (C) 1. U: user id 4. TC,S 5. (TC,S, request) ( 6. T' ) Ticket Structure: EK(S) {C, S, KC,S , timestamp, lifetime} CS 5204 – Operating Systems

  5. Kerberos • Phase 1 • 1. The user logs on to the client and the client asks for credentials for the user from Kerberos • U ­­> C : U (user id) • C ­­> K: (U, tgs) • 2. Kerberos constructs a ticket for U and tgs and a credential for the user and returns them to the client • Tu,tgs = EK(tgs) { U, tgs, KU,tgs , ts, lt} • K ­­> C: EK(U) {TU,tgs , KU,tgs , ts, lt} • The client obtains the user's password, P, and computes: • K'(U) = f(P) • The user is authenticated to the client if and only if K'(U) decrypts • the credential. CS 5204 – Operating Systems

  6. Kerberos • Phase 2 • 3. The client constructs an “authenticator” for user U and requests from TGS a ticket for server, S: • AU = E K(U,tgs) {C, ts } • C ­­> TGS : (S, TU,tgs , AU ) • 4. The server authenticates the request as coming from C and constructs a ticket with which C may use S: • TC,S = EK(S) { C, S, KC,S , ts, lt} • TGS ­­> C: EK(U,tgs) {TC,S , KC,S , ts, lt } CS 5204 – Operating Systems

  7. Kerberos • Phase 3 • 5. The client builds an authenticator and send it together with the ticket for the server to S: • AC = EK(C,S) { C, ts } • C ­­> S : (TC,S , AC ) • 6. The server (optionally) authenticates itself to the client by replying: • S ­­> C: E K(C,S) {ts + 1 } CS 5204 – Operating Systems

More Related