100 likes | 227 Views
QMCS 490 - Class Today. Homework due Today LAN and Internet Addresses Finish up Firewalls Routing Exercise Secret Key Management Wireshark. LAN and Internet Addresses. Let’s try to ‘map’ everyones’ addresses. Network Address Translation. Original purpose: more hosts & addresses
E N D
QMCS 490 - Class Today • Homework due Today • LAN and Internet Addresses • Finish up Firewalls • Routing Exercise • Secret Key Management • Wireshark R. Smith - University of St Thomas - Minnesota
LAN and Internet Addresses • Let’s try to ‘map’ everyones’ addresses R. Smith - University of St Thomas - Minnesota
Network Address Translation • Original purpose: more hosts & addresses • Let “insiders” use restricted addresses • Translate them on the way out • A ‘multiplexing’ mechanism • Users share a “real” Internet address R. Smith - University of St Thomas - Minnesota
Firewalls and LAN support • Provide a few standard LAN services • Router connection • DHCP R. Smith - University of St Thomas - Minnesota
Routing Exercise • Identify some ‘routers’ • The rest are ‘hosts’ R. Smith - University of St Thomas - Minnesota
Secret Key Management • Two elements • How do you assign individual keys • How do you update keys • Assignment – how many keys do we need? • “One Big Cryptonet” • Pairwise user-user • Pairwise user-server (“key distribution center) • Updating – given the assignment strategies • Manual • Automatic R. Smith - University of St Thomas - Minnesota
Automatic key updating • How do we get the new key? • Internal update • use a ‘pseudo random number generator’ • “Forward secrecy” problem • Random update • Use a new, randomly generated key • Share with the cryptonet • How do we transmit random keys? • Chained update • Send it using the existing crypto key • “Forward secrecy” problem • KEK-based update • Use a separate “key encrypting key” • Data is only sent with “data keys” or “session keys” • Only use KEK to send newly generated session R. Smith - University of St Thomas - Minnesota
Key Distribution Center (KDC) • Each user has a unique personal key • Contacts KDC to get a session key • KDC sends keys encrypted with users’ personal keys • Example • Bob wants to talk to Alice • Bob contacts KDC, says “I want to talk to Alice” • KDC sends two copies of the session key • One encrypted with Bob’s personal key • One encrypted with Alice’s personal key • This is the basis of Kerberos • Encrypted keys are called “tickets” R. Smith - University of St Thomas - Minnesota
Wireshark – to the lab! R. Smith - University of St Thomas - Minnesota
That’s it • Questions? Creative Commons License This work is licensed under the Creative Commons Attribution-Share Alike 3.0 United States License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/us/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. R. Smith - University of St Thomas - Minnesota