IT Security Basic - CH.2.2 Authentication
To prove you are who you say you are
- Password
- Certification authority (CA) - Organization / company to binds public key to particular entity
- Address
- Authentication Tokens
- Biometrics
- Fingerprints
- Voice Recognition
- Keystroke Timing
- Signatures
To register a Public Key in CA
- Money
- Proof of identity - I.E. ID Card, Staff Card
- CA uses their private key to sign on your Key, as to proof that "You are really you"
- There is a expiry time of signed keys
What do a Digital certificate looks like

To identify a public key(Bob) signed by CA
- Get the certificate signed with the public key [from the owner(B0b) /others] = A
- Sign the public key's certificate(the figure above) using CA's public key = B
- If A=B, then "Bob is really Bob"
Sample of Certificate (When you go to https websites, you can get it)


A real structure of a certificate

Chain of trust
- You have a CA(Name K) certificated a Public Key = A
- Your gf Marry trust you and you have private key = B with Marry
- As a result, if you sign A with B (A*B=C), Marry can use C and she will also trust the CA(K)

Trust Hierarchy
From the concept of chain of trust, the following hierarchy can be built

Attacks
Man-in-the-middle-attack
- A send password to B with A's IP address
- middle man (C) capture the password
- Drop A's messages
- Send B A's password and change the IP address to C itself
- B trust the password of A and believe C is A

Offline password attacks
Guess the correct password by test billions of times
Replay with fake address
Change victim's address to attacker's address

Key Management
KDC - Key Distribution Center, shares different secret key with each registered users
- Each user share a master key with KDC
- The master use to obtain a session key from KDC
- Master key may be distributed by "Post mail", face-to-face, pick up at Bank etc
KDC vs CA
- KDC stores real symmetric keys
- CA only identify a person, do not store many keys
- CA certificate can use during offline
- KDC must use online
- The server used by KDC called Kerberos
Preventing man-in-the-middle attack
Tickets
- Provide a real time authentication
- Use a non-internet channel to distribute
- Remember HSBC will give you a Black egg which will generate a number?
- The session key signed by ticket and the ticket will be expire every time after used
Global Clock synchronization
- Sync system time with NTP
- Detect delays caused by middle-man attack
More: http://web.mit.edu/kerberos/www/dialogue.html