Crypto U8 (part 2), Freshness

jjanesko
Mind Map by , created over 6 years ago

IYM002 (Unit 8 - randomness, freshness, AKE) Mind Map on Crypto U8 (part 2), Freshness, created by jjanesko on 04/23/2013.

63
10
0
jjanesko
Created by jjanesko over 6 years ago
Ciphers
Abraham Nwokolo
Ciphers
Abraham Nwokolo
PUBLIC KEY ENCRYPTION
Bhagya Prasad
Resumo global da matéria de Biologia e Geologia (10.º e 11.º anos)
miminoma
Geography Restless Earth
sophieelizabeth
Cryptography
Cher Bachar
SYMMETRIC ENCRYPTION
Bhagya Prasad
PUBLIC KEY ENCRYPTION
Bhagya Prasad
Cipher
Aina Syazwani
Introduction to Cryptography, Lecture 1
Jörg Schwartz
Crypto U8 (part 2), Freshness
1 freshness mechanism
1.1 techniques used to provide assurance that a message is new
1.1.1 i.e. a message is not a replay of an old message
1.2 not assurance of "aliveness" of sender because message could be delayed
2 3 kinds
2.1 sequence number
2.1.1 sender looks up a sequence number (counter) from a database & sends with message
2.1.1.1 receiver looks up sequence number in DB and compares with sent sequence number
2.1.2 challenges
2.1.2.1 sender and receiver must have databases
2.1.2.2 DBs must be synchronized
2.1.2.3 communication delays matter only if messages get mixed up
2.1.2.4 need a way to ensure integrity of sequence #
2.1.2.4.1 often a MAC is used to ensure that the sequence # has not been altered
2.2 clock based
2.2.1 message sent with a time stamp
2.2.1.1 receiver checks to see if time is within "window of acceptability"
2.2.2 challenges
2.2.2.1 sender and receiver must have clocks
2.2.2.2 clocks must be synchronized
2.2.2.2.1 problem with "clock drift"
2.2.2.2.2 need clock resync method
2.2.2.3 not useful for scenarios with big communication delays
2.2.2.4 needs a way to ensure the integrity of timestamp
2.2.2.4.1 often a MAC is used to ensure the timestamp has not been altered
2.3 nonce based
2.3.1 nonce = "number used only once"
2.3.1.1 sender creates nonce and sends to receiver with message
2.3.1.1.1 receiver sends response along with originally sent nonce
2.3.1.2 challenges
2.3.1.2.1 freshness requires 2 communication passes
2.3.1.2.2 does not required synchronization of clocks or DBs
2.3.1.2.3 sender must have access to a random number generator
2.3.1.2.4 does not provide message authentication
2.3.1.2.5 attacker may have guessed the nonce (unlikely)

Media attachments