- Greetings and Felicitations!
- More questions ... send to cs153@cs.ucdavis.edu the csif address seems to fail intermittently)
- Homework #2 will be available tomorrow on the web page

- Puzzle of the day
- Classical
- monoalphabetic (simple substitution):
*f*(*a*) =*a*+*k*mod*n* - example: Caesar with
*k*= 3,`RENAISSANCE`->`UHQDLVVDQFH` - polyalphabetic: Vigenère,
*f*(_{i}*a*) = (*a*+*k*) mod_{i}*n* - cryptanalysis: first do index of coincidence to see if it's monoalphabetic or polyalphabetic, then Kasiski method.
- problem: eliminate periodicity of key

- monoalphabetic (simple substitution):
- Long key generation
- Running-key cipher:
*M*=`THETREASUREISBURIED`;*K*=`THESECONDCIPHERISAN`;*C*=`MOILVGOFXTMXZFLZAEQ`; wedge is that (plaintext,key) letter pairs are not random (T/T, H/H, E/E, T/S, R/E, A/O, S/N, etc.) - Enigma/rotor systems; wheels, 3 rotors and a reflecting one. Go
through it; UNIX uses this for
*crypt*(1) command. - Perfect secrecy: when the probability of computing the plaintext message is the same whether or not you have the ciphertext
- Only cipher with perfect secrecy: one-time pads;
*C*=`AZPR`; is that`DOIT`or`DONT`?

- Running-key cipher:
- DES
- Go through the algorithm

- Public-Key Cryptography
- Basic idea: 2 keys, one private, one public
- Cryptosystem must satisfy:
- given public key, CI to get private key;
- cipher withstands chosen plaintext attack;
- encryption, decryption computationally feasible [note: commutativity notrequired]

- Benefits: can give confidentiality or authentiction or both

Some programs use passwords for access control, but do not protect the passwords in a very sophisticated manner (for example, by saving them in a file) or make determining the correct password very easy (for example, the Microsoft Word 5.0 encipherment scheme). The argument for using simple passwords and weak encipherment is that the data or programs being protected are of little value and the passwords give a small measure of privacy.

Given that what they are protecting is truly of little value, why is the use of such simple passwords and easily-broken encipherment bad?

Matt Bishop Office: 3059 Engineering Unit II Phone: +1 (530) 752-8060 Fax: +1 (530) 752-4767 Email: bishop@cs.ucdavis.edu | Copyright Matt Bishop, 2000. All federal and state copyrights reserved for all original material presented in this course through any medium, including lecture or print. |