Public Key Cryptography and Cryptographic Hashes: CS461/ECE422 Fall 2010
Public Key Cryptography and Cryptographic Hashes: CS461/ECE422 Fall 2010
Public Key Cryptography and Cryptographic Hashes: CS461/ECE422 Fall 2010
Cryptographic Hashes
CS461/ECE422
Fall 2010
Reading
Computer Security: Art and Science
Chapter 9
Handbook of Applied Cryptography, Chapter
8
http://www.cacr.math.uwaterloo.ca/hac/
Public-Key Cryptography
Slide #9-3
Public Key Cryptography
Two keys
Private key known only to individual
Public key available to anyone
Idea
Confidentiality: encipher using public key,
decipher using private key
Integrity/authentication: encipher using private
key, decipher using public one
Slide #9-4
Requirements
1. It must be computationally easy to
encipher or decipher a message given the
appropriate key
2. It must be computationally infeasible to
derive the private key from the public key
3. It must be computationally infeasible to
determine the private key from a chosen
plaintext attack
Slide #9-5
General Facts about Public Key
Systems
Public Key Systems are much slower than
Symmetric Key Systems
RSA 100 to 1000 times slower than DES. 10,000 times
slower than AES?
Generally used in conjunction with a symmetric system
for bulk encryption
Public Key Systems are based on hard problems
Factoring large composites of primes, discrete
logarithms, elliptic curves
Only a handful of public key systems perform
both encryption and signatures
Slide #9-6
Diffie-Hellman
The first public key cryptosystem proposed
Usually used for exchanging keys securely
Compute a common, shared key
Called a symmetric key exchange protocol
Based on discrete logarithm problem
Given integers n and g and prime number p, compute k
such that n = gk mod p
Solutions known for small p
Solutions computationally infeasible as p grows large
Slide #9-7
Algorithm
Public Constants: prime p, integer g 0, 1, or p1
Choose private keys and compute public keys
Anne chooses private key kAnne,
computes public key KAnne = gkAnne mod p
Similarly Bob chooses kBob,
computes Kbob = gkBob mod p
Exchange public keys and compute shared information
To communicate with Bob, Anne computes Kshared =
KBobkAnne mod p
To communicate with Anne, Bob computes Kshared =
KAnnekBob mod p Slide #9-8
Working the Equations
(KBob)kAnne mod p
= (gkBob mod p) kAnne mod p
= gkBob kAnne mod p
(Kalice)kBob mod p
= (gkAlice mod p)kBob mod p
= gkAlice kBob mod p
Slide #9-12
Modular Arithmetic
a mod b = x if for some k >= 0, bk + x = a
Associativity, Commutativity, and
Distributivity hold in Modular Arithmetic
Inverses also exist in modular arithmetic
a + (-a) mod n = 0
a * a-1 mod n = 1
Modular Arithmetic
Reducibility also holds
(a + b) mod n = (a mod n + b mod n) mod n
a * b mod n = ((a mod n) * b mod n) mod n
Fermats Thm: if p is any prime integer and
a is an integer, then ap mod p = a
Corollary: ap-1 mod p = 1 if a != 0 and a is
relatively prime to p
Background
Totient function (n)
Number of positive integers less than n and relatively
prime to n
Relatively prime means with no factors in common with n
Example: (10) = ?
4 because 1, 3, 7, 9 are relatively prime to 10
Example: (p) = ? where p is a prime
p-1 because all lower numbers are relatively prime
Slide #9-15
Background
Euler generalized Fermats Thm for
composite numbers.
Recall Fermat's Thm ap-1=1 mod p if a != 0
Slide #9-21
Example: Confidentiality
Take p = 7, q = 11, so n = 77 and (n) = 60
Alice chooses e = 17, making d = 53
Bob wants to send Alice secret message HELLO
(07 04 11 11 14)
0717 mod 77 = 28
0417 mod 77 = 16
1117 mod 77 = 44
1117 mod 77 = 44
1417 mod 77 = 42
Bob sends 28 16 44 44 42
Slide #9-22
Example
Alice receives 28 16 44 44 42
Alice uses private key, d = 53, to decrypt message:
2853 mod 77 = 07
1653 mod 77 = 04
4453 mod 77 = 11
4453 mod 77 = 11
4253 mod 77 = 14
Alice translates message to letters to read HELLO
No one else could read it, as only Alice knows her
private key and that is needed for decryption
Slide #9-23
Example:
Integrity/Authentication
Take p = 7, q = 11, so n = 77 and (n) = 60
Alice chooses e = 17, making d = 53
Alice wants to send Bob message HELLO (07 04 11 11 14)
so Bob knows it is what Alice sent (no changes in transit,
and authenticated)
0753 mod 77 = 35
0453 mod 77 = 09
1153 mod 77 = 44
1153 mod 77 = 44
1453 mod 77 = 49
Alice sends 35 09 44 44 49
Slide #9-24
Example
Bob receives 35 09 44 44 49
Bob uses Alices public key, e = 17, n = 77, to decrypt message:
3517 mod 77 = 07
0917 mod 77 = 04
4417 mod 77 = 11
4417 mod 77 = 11
4917 mod 77 = 14
Bob translates message to letters to read HELLO
Alice sent it as only she knows her private key, so no one else could have
enciphered it
If (enciphered) messages blocks (letters) altered in transit, would not
decrypt properly
Slide #9-25
Example: Both
Alice wants to send Bob message HELLO both enciphered
and authenticated (integrity-checked)
Alices keys: public (17, 77); private: 53
Bobs keys: public: (37, 77); private: 13
Alice enciphers HELLO (07 04 11 11 14):
(0753 mod 77)37 mod 77 = 07
(0453 mod 77)37 mod 77 = 37
(1153 mod 77)37 mod 77 = 44
(1153 mod 77)37 mod 77 = 44
(1453 mod 77)37 mod 77 = 14
Alice sends 07 37 44 44 14
Slide #9-26
Warnings
Encipher message in blocks considerably
larger than the examples here
If 1 character per block, RSA can be broken
using statistical attacks (just like classical
cryptosystems)
Attacker cannot alter letters, but can rearrange
them and alter message meaning
Example: reverse enciphered message of text ON to
get NO
Slide #9-27
Direct Digital Signature
Involve only sender & receiver
Assumed receiver has senders public-key
Digital signature made by sender signing
entire message or hash with private-key
Can encrypt using receivers public-key
Security depends on senders private-key
Slide #9-28
Potential problems
Alice
Bob
Carol
Sign-Encrypt vs. Encrypt-Sign
Is Sign-Encrypt Enough?
Recipient knows who wrote the message
But who encrypted it?
Surreptitious forwarding
Does Encrypt-Sign make sense?
Signature can be easily replaced
RSA Signatures
Slide #9-30
Hash or Checksums
Mathematical function to generate a set of k
bits from a set of n bits (where k n).
k is smaller then n except in unusual
circumstances
Example: ASCII parity bit
ASCII has 7 bits; 8th bit is parity
Even parity: even number of 1 bits
Odd parity: odd number of 1 bits
Slide #9-32
Example Use
Bob receives 10111101 as bits.
Sender is using even parity; 6 1 bits, so
character was received correctly
Note: could be garbled, but 2 bits would need to
have been changed to preserve parity
Sender is using odd parity; even number of 1
bits, so character was not received correctly
Slide #9-33
Another Example
8-bit Cyclic Redundancy Check (CRC)
XOR all bytes in the file/message
Good for detecting accidental errors
But easy for malicious user to fix up to match altered
message
For example, change the 4th bit in one of the bytes
Fix up by flipping the 4th bit in the CRC
Easy to find a M that has the same CRC
Slide #9-34
Cryptographic Hash or
Checksum or Message Digest
h: AB:
For any x A, h(x) is easy to compute
For any y B, it is computationally infeasible to
find x A such that h(x) = y
One way function, e.g., computing x3 vs cube
root of x by hand
It is computationally infeasible to find two inputs x,
x A such that x x and h(x) = h(x)
Alternate form: Given any x A, it is computationally
infeasible to find a different x A such that
h(x) = h(x).
Slide #9-35
Collisions
If x x and h(x) = h(x), x and x are a
collision
Pigeonhole principle: if there are n containers
for n+1 objects, then at least one container will
have 2 objects in it.
Application: if there are 32 files and 8 possible
cryptographic checksum values, at least one
value corresponds to at least 4 files
How many files until you are guaranteed a
collision? Until you probably have a collision?
Slide #9-36
Birthday Paradox
What is the probability that someone in the
room has the same birthday as me?
What is the probability that two people in the
room have the same birthday?
P(n) = 1 (365!/(365n*(365-n)!)
P(n) > for n = 23
Section 2.15 Handbook of Applied
Cryptography
http://en.wikipedia.org/wiki/Birthday_paradox
Birthday Paradox
In general, probability of a collision of
reaches 50% for M units when
n = sqrt(M)
If hash has m bits, this means M = 2m
possible hash values
n = 2m/2 for 50% probability collision
Another View of Collisions
Birthday attack works thus:
opponent generates 2m/2 variations of a valid message
all with essentially the same meaning
opponent also generates 2m/2 variations of a desired
fraudulent message
two sets of messages are compared to find pair with
same hash (probability > 0.5 by birthday paradox)
have user sign the valid message, then substitute the
forgery which will have a valid signature
Need to use larger MACs
Slide #9-39
MD5 and SHA
Most widely used keyless crypto hashes
Both are round based bit operations
Similar in spirit to AES and DES
Looking for avalanche effect to make output
appear random
MD5 is 128 bits and SHA-1 is 160 bits
Slide #9-40
More on SHA
Standard put forth by NIST
SHA spec
http://csrc.nist.gov/CryptoToolkit/tkhash.html
Comes in different flavors that vary based
on output size
SHA-1 outputs 160 bits
The other SHA-X flavors output X bits
Slide #9-41
SHA-1 Broken
Chinese researchers had a break through
http://www.schneier.com/blog/archives/2005/02/
sha1_broken.html
Recent results show that you can find collisions in 2^69
attempts which would be less than 2^80 from brute force
Does not affect HMAC-SHA
NIST published standards promoting using of
larger SHA's
http://csrc.nist.gov/groups/ST/toolkit/secure_hashing.ht
ml
Preparing for public competition for new algorithmSlide #9-42
Keyed vs Keyless Hash
Keyless hash anyone can recompute given
the message and indication of the algorithm
Keyed hash must have access to a key to
recompute the hash
When is each option appropriate?
Message Authentication Codes
MAC is a crypto hash that is a proof of a
messages integrity
Important that adversary cannot fixup MAC if
he changes message
MACs rely on keys to ensure integrity
Either Crypto Hash is encrypted already
Or Crypto Hash must be augmented to take a
key
Slide #9-44
Use Symmetric Ciphers for Keyed
Hash
Can use DES or AES in CBC mode
Last block is the hash
DES with 64 bit block size is too small to be
effective MAC
Slide #9-45
HMAC
Make keyed cryptographic checksums from
keyless cryptographic checksums
h keyless cryptographic checksum function that
takes data in blocks of b bytes and outputs blocks
of l bytes. k is cryptographic key of length b bytes
ipad is 00110110 repeated b times
opad is 01011100 repeated b times
HMAC-h(k, m) = h(k opad || h(k ipad || m))
exclusive or, || concatenation
Slide #9-46
Key Points
Symmetric cryptosystems encipher and decipher
using the same key
Or one key is easily derived from the other
Public key cryptosystems encipher and decipher
using different keys
Computationally infeasible to derive one from the other
Cryptographic checksums provide a check on
integrity
Slide #9-47