Return to Question

deleted 9 characters in body; edited title

Source Link

edited Dec 28, 2013 at 19:21

Few things i don't fully understand about ssl SSL handshake: what makes it unforgeable?

I understand the ssl handshake flow, but still need few verifications:

If I'm trying to forge another handshake the client will fail because, and only because the certificate I'll send him back is not trusted?
iI understand that the session keys (symmetric) are used to decrypt/and encrypt the data.

whereWhere are those stored in the client?
if iIf I go to a client computer, get this session key, can i decrypt all the data sent to the server? (iI mean, isntisn't the traffic encrypted with the public key from the server?)

Also, iI understand that the handshake can be sent during the flow to keep it more secured, if the certificate is not trusted, does the connection ends now? (because in the first step, i understand that the user can decide to go further with a warning in his browser that the certificate cannot be trusted).

thanks

I understand the ssl handshake flow, but still need few verifications:

If I'm trying to forge another handshake the client will fail because, and only because the certificate I'll send him back is not trusted?
i understand that the session keys (symmetric) are used to decrypt/and encrypt the data.

where are those stored in the client?
if i go to a client computer, get this session key, can i decrypt all the data sent to the server? (i mean, isnt the traffic encrypted with the public key from the server?)

Also, i understand that the handshake can be sent during the flow to keep it more secured, if the certificate is not trusted, does the connection ends now? (because in the first step, i understand that the user can decide to go further with a warning in his browser that the certificate cannot be trusted).

thanks

I understand the ssl handshake flow, but still need few verifications:

If I'm trying to forge another handshake the client will fail because, and only because the certificate I'll send him back is not trusted?
I understand that the session keys (symmetric) are used to decrypt/and encrypt the data.

Where are those stored in the client?
If I go to a client computer, get this session key, can i decrypt all the data sent to the server? (I mean, isn't the traffic encrypted with the public key from the server?)

Also, I understand that the handshake can be sent during the flow to keep it more secured, if the certificate is not trusted, does the connection ends now? (because in the first step, i understand that the user can decide to go further with a warning in his browser that the certificate cannot be trusted).

Source Link

asked Dec 28, 2013 at 18:58

I understand the ssl handshake flow, but still need few verifications:

If I'm trying to forge another handshake the client will fail because, and only because the certificate I'll send him back is not trusted?
i understand that the session keys (symmetric) are used to decrypt/and encrypt the data.

where are those stored in the client?
if i go to a client computer, get this session key, can i decrypt all the data sent to the server? (i mean, isnt the traffic encrypted with the public key from the server?)

Also, i understand that the handshake can be sent during the flow to keep it more secured, if the certificate is not trusted, does the connection ends now? (because in the first step, i understand that the user can decide to go further with a warning in his browser that the certificate cannot be trusted).

thanks

tls