Outline for February 28, 2003
Reading: text, §10.4 (except 10.4.1), 10.5.2, 10.6, 11.1, 11.3, 11.4.1, 12.1-12.2.2
Discussion Problem
"To fight and conquer in all your battles is not supreme
excellence; supreme excellence consists in breaking the enemy's
resistance without fighting. In the practical art of war, the best thing
of all is to take the enemy's country whole and intact; to shatter and
destroy it is not so good. So, too, it is better to capture an army
entire than to destroy it, to capture a regiment, a detachment, or a
company entire than to destroy it."1
What does this paragraph say to a system administrator or security
officer seeking insight to defend her systems?
Outline for the Day
- Cryptographic Key Infrastructure
- Certificates (X.509, PGP)
- Certificate, key revocation
- Digital Signatures
- Judge can confirm, to the limits of technology, that claimed signer did sign message
- RSA digital signatures: sign, then encipher
- Types of attacks
- Forward searches
- Misordered blocks
- Statistical regularities (repetitions)
- Networks and ciphers
- Where to put the encryption
- Link vs. end-to-end
- Example protocol: PEM
- Design goals
- How it was done
- Differences between it and PGP
- Authentication
- Basis: what you know/have/are, where you are
- Passwords
- How UNIX does selection
- Problem: common passwords
- May be pass phrases: goal is to make search space as large as possible, distribution as uniform as possible
- Other ways to force good password selection: random, pronounceable, computer-aided selection
- Go through problems, approaches to each, esp. proactive
- Password Storage
- In the clear; MULTICS story
- Enciphered; key must be kept available; get to it and it's all over
- Hashed; present idea of one-way functions using identity and sum; show UNIX version, including salt
- Attack Schemes Directed to the Passwords
- Exhaustive search: UNIX is 1-8 chars, say 96 possibles; it's about 7e16
- Inspired guessing: think of what people would like (see above)
- Random guessing: can't defend against it; bad login messages aid it
- Scavenging: passwords often typed where they might be recorded (b\as login name, in other contexts, etc.
- Ask the user: very common with some public access services
- Expected time to guess