









Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Data Communication and Networking powerpoint slide
Typology: Slides
1 / 16
This page cannot be seen from the preview
Don't miss anything!










[Compressed] Data
[Compressed] Data MAC
Padding
Padding
TCP Header
TCP Header
Record Header
Record Header
n * Block Cipher Size
Record Body
Record Body
Application Data (Segment 1)
Application Data (Segment 1)
Record Header
Record Header
Application Data (Segment 2)
Application Data (Segment 2)
5 Bytes
Server
Server Hello
Server Hello
R
S
S
ServerHelloDone
ServerHelloDone
Client
Client Hello
Client Hello
R
C
C
Application Data°
Application Data°
Application Data°
Application Data°
Certificate*
ClientKeyExchange
CertificateVerify*
*optional
ServerKeyExchange*
Certificate*
CertificateRequest*
*optional
Finished°
Finished°
ChangeCipherSpec
Finished°
Finished°
ChangeCipherSpec
°encrypted
Initially developed by Netscape
SSL 2.0 is sensitive to man-in-the-middle attacks leading
e.g. to the negotiation of weak encryption keys
SSL 2.0 should not be used anymore
Internet Draft authored by Netscape, November 1996
Supported by all browsers
Vulnerable to the BEAST Cipher-Block-Chaining (CBC) attack
IETF RFC 2246, January 1999
TLS 1.0 ist not backwards compatible to SSL 3.0 (differences
in
MAC computation, PRF function for master_secret and key
material)
Supported by all browsers
Vulnerable to the BEAST Cipher-Block-Chaining (CBC) attack
Thai Duong and Juliano Rizzo presented their exploit on
September 23 2011 at the 7th ekoparty Security Conference
in Buenos Aires.
The exploit uses a known-plaintext attack on the Cipher-Block-
Chaining (CBC) encryption vulnerability of SSL 3.0 and TLS 1.
which has been known since 2001 and was fixed by TLS 1.1 in
The BEAST JavaScript code running in a browser decrypts
encrypted cookies sent via HTTPS within a couple of seconds.
Temporary workaround: Set up HTTPS web servers with
stream ciphers (e.g. the rather outdated RC4 algorithm)
Migration of HTTPS web servers and browsers to TLS 1.1 or