1 / 24

ECE 454/599 Computer and Network Security

ECE 454/599 Computer and Network Security. Dr. Jinyuan (Stella) Sun Dept. of Electrical Engineering and Computer Science University of Tennessee Fall 2012. Exercise: Chapters 13, 15-18. 1. [Kaufman] 13.1

coreen
Download Presentation

ECE 454/599 Computer and Network Security

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. ECE 454/599 Computer and Network Security Dr. Jinyuan (Stella) Sun Dept. of Electrical Engineering and Computer Science University of Tennessee Fall 2012

  2. Exercise: Chapters 13, 15-18

  3. 1. [Kaufman] 13.1 Design a variant of Kerberos in which the workstation generates a TGT. The TGT will be encrypted with the user’s master key rather than the KDC’s master key. How does this compare with standard Kerberos in terms of efficiency, security, etc.? What happens in each scheme if the user changes her password during a login session?

  4. 1. [Kaufman] 13.1

  5. 2. [Kaufman] 15.4 Compare the following schemes for obtaining Bob's public key, in terms of bandwidth and computation efficiency, security, flexibility, and any other criteria you can think of: downloading Bob's key from the node located at a particular IP address (via an unauthenticated interaction), looking up Bob's key in a directory via an unauthenticated interaction, having an authenticated conversation to the directory, having the directory sign the information you request, storing and retrieving certificates from the directory, having no directory but having each principal responsible for keeping its own certificate and sending it to someone who needs to talk to it.

  6. 2. [Kaufman] 15.4

  7. 3. [Kaufman] 16.7 Devise a protocol based on a pre-shared secret key that hides identities and gives PFS for identity hiding. Make two variants, one in which an active attacker can learn only the initiator's identity, and one in which an active attacker can learn only the target's identity.

  8. 3. [Kaufman] 16.7

  9. 4. [Kaufman] 16.11 In the Protocol 16-6, explain why Bob knows that Alice is the real Alice, and not someone replaying Alice's messages. How does Alice know that it's the real Bob if she uses a different a each time? Modify the protocol to allow both Alice and Bob to reuse their a and b values, and yet have both sides be able to know they are talking to a live partner.

  10. 4. [Kaufman] 16.11

  11. 5. [Kaufman] 17.1 Suppose Alice is sending packets to Bob using IPsec. Suppose Bob's TCP acknowledgment gets lost, and Alice's TCP, assuming the packet was lost, retransmits the packet. Will Bob's IPsec implementation notice that the packet is a duplicate and discard it?

  12. 5. [Kaufman] 17.1 No. IPsec treats a retransmitted TCP packet as a new IPsec packet. It is up to TCP to notice the packet is a duplicate.

  13. 6. [Kaufman] 17.4 Would it be possible for the SA to be defined only by the destination address and the SPI (i.e., leave out whether it's ESP or AH)? Would this require any changes to the IPsec protocol? Would an implementation of a receiver that defined the SA based solely on destination address and SPI interwork with one that did what the IPsec specification says?

  14. 6. [Kaufman] 17.4

  15. 7. [Kaufman] 17.5 When sending encrypted traffic from firewall to firewall, why does there need to be an extra IP header? Why can't the firewall simply encrypt the packet, leaving the source and destination as the original source and destination?

  16. 7. [Kaufman] 17.5

  17. 8. [Stallings] 16.4 The IPsec architecture document states that when two transport mode SA's are bundled to allow both AH and ESP protocols on the same end-to-end flow, only one ordering of security protocols seems appropriate: performing the ESP protocol before performing the AH protocol. Why is this approach recommended rather than authentication before encryption?

  18. 8. [Stallings] 16.4 This order of processing facilitates rapid detection and rejection of replayed or bogus packets by the receiver, prior to decrypting the packet, hence potentially reducing the impact of denial of service attacks. It also allows for the possibility of parallel processing of packets at the receiver, i.e., decryption can take place in parallel with authentication.

  19. 9. [Kaufman] 18.1 Suppose if Alice's aggressive-mode IKE connection initiate is refused, Alice starts up another aggressive-mode connection initiate with her next (and weaker) choice of Diffie-Hellman group, rather than starting a main-mode exchange telling Bob all her supported Diffie-Hellman groups. What is the vulnerability, given an active attacker?

  20. 9. [Kaufman] 18.1 The active attacker can trick Alice into using weak crypto. The bad guy can impersonate Bob and refuse Alice’s strong crypto proposal. Then Alice will retry with a weaker proposal.

  21. 10. [Kaufman] 18.5 How can you modify aggressive mode with public signature keys (see §18.5.10.2 Public Signature Keys, Aggressive Mode) to hide the endpoint identifiers from eavesdroppers? Which identity will be hidden from an active attacker? Give a disadvantage of this.

  22. 10. [Kaufman] 18.5

  23. 11. [Kaufman] 18.8 Design a protocol in which authentication is one-way since only one side has a public key. Do the protocol with a public signature key. Now do it with a public encryption key.

  24. 11. [Kaufman] 18.8

More Related