1 / 25

EEC 688/788 Secure and Dependable Computing

EEC 688/788 Secure and Dependable Computing. Lecture 6 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University wenbing@ieee.org. Outline. Reminder: no class next Monday 2/21 (President’s day) Midterm #1 Results Authentication Concept

jacobss
Télécharger la présentation

EEC 688/788 Secure and Dependable Computing

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. EEC 688/788Secure and Dependable Computing Lecture 6 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University wenbing@ieee.org

  2. Outline Reminder: no class next Monday 2/21 (President’s day) Midterm #1 Results Authentication Concept General model for authentication protocols Authentication protocols Authentication Based on a Shared Secret Key Establishing a Shared Key: Diffie-Hellman Authentication Using a Key Distribution Center Authentication Using Public-Key Cryptography Attacks on authentication protocols EEC688/788: Secure & Dependable Computing

  3. Midterm #1 Results High 95, low 32, average: 70 Q1: 40.5/50, Q2: 8.5/10, Q3: 13/20, Q4: 8/20 EEC688/788: Secure & Dependable Computing

  4. Authentication Protocols Authenticationis the technique by which a process verifies that its communication partner is who it is supposed to be and not an imposter Verifying the identity of a remote process in the face of a malicious, active intruder is surprisingly difficult and requires complex protocols based on cryptography Not to be confused with authorization Authorization is concerned with what process is permitted to do EEC688/788: Secure & Dependable Computing

  5. Authorization Authentication: Verify the claim that a subject says it is S: verifying the identity of a subject Authorization: Determining whether a subject is permitted certain services from an object Note: authorization makes sense only if the requesting subject has been authenticated EEC688/788: Secure & Dependable Computing

  6. General Model for Authentication Protocols Alice starts out by sending a message either to Bob or to a trusted KDC (Key Distribution Center), which is expected to be honest Several other message exchanges follow in various directions Trudy may intercept, modify, or replay the messages transmitted to trick Alice and Bob When the protocol has been completed, Alice is sure she is talking to Bob and Bob is sure he is talking to Alice EEC688/788: Secure & Dependable Computing

  7. General Model for Authentication Protocols In general, the authentication process also produce a secret session key for use in the upcoming conversation For each new connection, a new, randomly-chosen session key should be used Public-key cryptography is widely used for the authentication protocols themselves and for establishing the session key EEC688/788: Secure & Dependable Computing

  8. Why Use a Session Key For performance reasons, symmetric key encryption is much faster than public-key encryption To minimize the amount of traffic that gets sent with the users’ secret keys These keys are used to establish the secure session To reduce the amount of ciphertext encrypted using the same key which an intruder can obtain If a session key is broken, only info sent in that session is exposed To minimize the damage done if a process crashes and its core dump falls into the wrong hands. Hopefully, the only key present then will be the session key All the permanent keys should have been carefully zeroed out after the session was established EEC688/788: Secure & Dependable Computing

  9. Authentication Protocols Authentication Based on a Shared Secret Key Establishing a Shared Key: Diffie-Hellman Authentication Using a Key Distribution Center Authentication Using Public-Key Cryptography EEC688/788: Secure & Dependable Computing

  10. Authentication Based on a Shared Secret Key Two-way authentication using a challenge-response protocol Challenge-response: one party sends a random number to the other, who then transforms it in a special way and then returns the result Nonces: random numbers used just once in challenge-response protocols Assume that Alice and Bob already share a secret key, KAB EEC688/788: Secure & Dependable Computing

  11. Authentication Based on a Shared Secret Key EEC688/788: Secure & Dependable Computing

  12. Authentication Based on a Shared Secret Key A shortened two-way authentication protocol. Is this new protocol an improvement over the original one ? It is shorter But it is also wrong Under certain circumstances, Trudy can defeat this protocol by using what is known as a reflection attack EEC688/788: Secure & Dependable Computing

  13. Reflection Attack The reflection attack: Trudy can break it if it is possible to open multiple sessions with Bob at once This attack can be defeated by encrypting RB with KAB in message 2 EEC688/788: Secure & Dependable Computing

  14. General Rules for Authentication Protocols Design Rule#1: Have the initiator prove who she is before the responder has to In the previous case, Bob gives away valuable information before Trudy has to give any evidence of who she is Rule#2: Have the initiator and responder use different keys for proof, e.g., KABand K'AB Rule#3: Have the initiator and responder draw their challenges from different sets E.g., the initiator uses even numbers, the responder uses odd numbers Rule#4: Be aware of parallel sessions (no info flows across different sessions) EEC688/788: Secure & Dependable Computing

  15. Establishing a Shared Key:The Diffie-Hellman Key Exchange A protocol that leads to the establishment of a shared secrete key is called key agreement protocol or key exchange protocol Diffie-Hellman key exchange Two large numbers, n and g, where n is a prime, (n - 1)/2 is also a prime and certain conditions apply to g EEC688/788: Secure & Dependable Computing

  16. Establishing a Shared Key:The Diffie-Hellman Key Exchange EEC688/788: Secure & Dependable Computing

  17. Establishing a Shared Key:The Diffie-Hellman Key Exchange Example: n = 47 and g = 3. Alice picks x = 8 and Bob picks y = 10. Both of these are kept secret Alice's message to Bob is (47, 3, 28) because 38 mod47 is 28. Bob's message to Alice is (17) Alice computes 178 mod 47, which is 4 Bob computes 2810 mod 47, which is 4 Alice and Bob have independently determined that the secret key is now 4 Trudy has to solve the equation 3xmod 47 = 28 EEC688/788: Secure & Dependable Computing

  18. Establishing a Shared Key:The Diffie-Hellman Key Exchange The man-in-the-middle attack When Bob gets (47, 3, 28), how does he know it is from Alice and not from Trudy? There is no way he can know Trudy can exploit this fact to deceive both Alice and Bob EEC688/788: Secure & Dependable Computing

  19. Man-In-The-Middle Attack A man-in-the-middle attack (MITM) is an attack in which an attacker is able to read, insert and modify at will, messages between two parties without either party knowing that the link between them has been compromised The attacker must be able to observe and intercept messages going between the two victims EEC688/788: Secure & Dependable Computing

  20. Authentication Using a Key Distribution Center Each user has a single key shared with the KDC. Authentication and session key management now goes through the KDC The following protocol is subject to replay attack EEC688/788: Secure & Dependable Computing

  21. Needham-Schroeder Authentication Protocol Needham-Schroeder protocol: a multi-way challenge-response protocol To eliminate the possibility of replay attacks, have each party both generate a challenge and respond to one EEC688/788: Secure & Dependable Computing

  22. Needham-Schroeder Authentication Protocol Message 1: RA is a nonce Message 2: KB(A, KS) is ticket Alice will send to Bob RA: so that message 2 is not a replay B: so that if Trudy replaces B with her id in message 1, it will be detected Ticket is encrypted using Bob’s key KB so that Trudy cannot replace it with something else on the way back to Alice EEC688/788: Secure & Dependable Computing

  23. Needham-Schroeder Authentication Protocol Message 3: a new nonce RA2 is used Message 4: Bob sends back KS(RA2-1) instead of KS(RA2) so that Trudy cannot steal KS(RA2) from message 3 and replay it here Message 5: to convince Bob he is talking to Alice and no replays are being used EEC688/788: Secure & Dependable Computing

  24. Authentication Using Public-Key Cryptography EEC688/788: Secure & Dependable Computing

  25. Authentication Using Public-Key Cryptography • What can Trudy do to try to subvert this protocol? • She can fabricate message 3 and trick Bob into probing Alice, but Alice (from message 6) will see an RAthat she did not send and will not proceed further • Trudy cannot forge message 7 back to Bob because she does not know RBor KSand cannot determine them without Alice's private key EEC688/788: Secure & Dependable Computing

More Related