1 / 21

Eran Tromer Slide credits: John Mitchell, Stanford

Introduction to Information Security 0368-3065, Spring 2014 Lecture 5: Cryptography overview (1/2). Eran Tromer Slide credits: John Mitchell, Stanford. History of crypto. Ceaser cipher Electromechanical ciphers (e.g., Enigma) Information theory Complexity theory Modern cryptography.

tan
Download Presentation

Eran Tromer Slide credits: John Mitchell, Stanford

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. Introduction to Information Security0368-3065, Spring 2014Lecture 5: Cryptography overview (1/2) Eran TromerSlide credits:John Mitchell, Stanford

  2. History of crypto • Ceaser cipher • Electromechanical ciphers(e.g., Enigma) • Informationtheory • Complexitytheory • Moderncryptography

  3. Cryptography • Is • A tremendous tool • The basis for many security mechanisms • Is not • The solution to all security problems • Reliable unless implemented properly • Reliable unless used properly • Something you should try to invent yourself unless • you spend a lot of time becoming an expert • you subject your design to outside review

  4. Scenarios • Storage • Store files privately • Protect files from tampering • Communication • Avoid eavesdropping • Avoid corruption • “Secure channel” • Authentication • Many protocols

  5. Basic cryptographic concepts • Encryption scheme: • functions to encrypt, decrypt data • Symmetric encryption • Block, stream ciphers • Hash function, MAC • Map any input to short hash; ideally, no collisions • MAC (keyed hash) used for message integrity • Public-key cryptography • PK encryption: public key does not reveal key-1 • Signatures: sign data, verify signature

  6. Symmetric cryptography schemes

  7. Symmetric encryption E, D: cipher k: secret key (e.g., 128 bits) m, c: plaintext, ciphertextn: nonce (aka IV) Kerckhoff’s Principle A cryptosystem should be secure even if everything about the system, except the key, is public knowledge. (Never use a proprietary cipher.) Keygeneration k k m, n D(k,c,n)=m E c, n D E(k,m,n)=c Alice Bob

  8. First example: One Time Pad (single use key) 0 1 1 1 0 1 0 0 0 1 1 0 1 0 1 1 0 1 1 1 0 0 0 0 1 0 1 0 0 0 • Vernam (1917) • Shannon ‘49: • OTP is “secure” against ciphertext-only attacks Key:  Plaintext: Ciphertext:

  9. Stream ciphers (single use key) Problem: OTP key is as long the message Solution: Pseudo random key -- stream ciphers Example: RC4 key c  PRBG(k)  m PRBG  message ciphertext

  10. Dangers in using stream ciphers One time key! “Two time pad” is insecure: C1 m1  PRBG(k) C2 m2  PRBG(k) Eavesdropper does: C1  C2  m1  m2 Enough redundant information in English that: m1  m2  m1 , m2

  11. Symmetric encryption: nonce (IV) E, D: cipher k: secret key (e.g., 128 bits) m, c: plaintext, ciphertext n: nonce (aka IV) nonce Alice Bob m, n D(k,c,n)=m E c, n D E(k,m,n)=c k k

  12. Use Cases • Single use key: (one time key) • Key is only used to encrypt one message • encrypted email: new key generated for every email • No need for nonce (set to 0) • Multi use key: • Key used to encrypt multiple messages • SSL: same key used to encrypt many packets • Need either unique nonce or random nonce • Multi use key, but all plaintexts are distinct: • Can eliminate nonce (use 0) using special mode (SIV)

  13. Block ciphers: crypto work horse n Bits n Bits E, D PT Block CT Block Key k Bits • Canonical examples: • 3DES: n= 64 bits, k = 168 bits • AES: n=128 bits, k = 128, 192, 256 bits • IV handled as part of PT block

  14. Building a block cipher mL mR mR  mLF(k,mR) Input: (m, k) Repeat simple mixing operation several times  DES: Repeat 16 times:(“Feistel” structure)  AES-128: Mixing step repeated 10 times Difficult to design: must resist subtle attacks  differential attacks, linear attacks, brute-force, …

  15. Block Ciphers Built by Iteration key k R(k,m): round function for DES (n=16), for AES (n=10) key expansion k1 k2 k3 kn m c R(k1, ) R(k2, ) R(k3, ) R(kn, )

  16. Incorrect use of block ciphers • Electronic Code Book (ECB): • Problem: • if m1=m2 then c1=c2 PT: m1 m2 c2 c1 CT:

  17. In pictures [visual comparison by Bart Preneel]

  18. Correct use of block ciphers I: CBC mode E a secure PRP. Cipher Block Chaining with IV: IV m[0] m[1] m[2] m[3]     E(k,) E(k,) E(k,) E(k,) IV c[0] c[1] c[2] c[3] ciphertext Q: how to do decryption?

  19. In pictures

  20. Correct use of block ciphers II: CTR mode Counter mode with a random IV: (parallel encryption) IV m[0] m[1] … m[L]  E(k,IV) E(k,IV+1) … E(k,IV+L) IV c[0] c[1] … c[L] ciphertext • Why are these modes secure? not today.

  21. Hash functions and message integrity (see next talk’s slides)

More Related