Skip to main content
added 4 characters in body
Source Link

Reference to SSL 2.0 specs. from: Mozilla - SSL 2.0 Can I conclude that SSL 2.0 Finish messages does not provide AMC for all the messages sent/received by both parties (as in TLS 1.2)? Due to lack of SSL 2.0 official detailed documentation, I am unable to confirm this.

2.2.1 Assuming no session-identifier

2.2.1 Assuming no session-identifier

client-hello         C -> S: challenge, cipher_specs
server-hello         S -> C: connection-id,server_certificate,cipher_specs
client-master-key    C -> S: {master_key}server_public_key
client-finish        C -> S: {connection-id}client_write_key
server-verify        S -> C: {challenge}server_write_key
server-finish        S -> C: {new_session_id}server_write_key

Reference to SSL 2.0 specs. from: Mozilla - SSL 2.0 Can I conclude that SSL 2.0 Finish messages does not provide AMC for all the messages sent/received by both parties (as in TLS 1.2)? Due to lack of SSL 2.0 official detailed documentation, I am unable to confirm this.

2.2.1 Assuming no session-identifier

client-hello         C -> S: challenge, cipher_specs
server-hello         S -> C: connection-id,server_certificate,cipher_specs
client-master-key    C -> S: {master_key}server_public_key
client-finish        C -> S: {connection-id}client_write_key
server-verify        S -> C: {challenge}server_write_key
server-finish        S -> C: {new_session_id}server_write_key

Reference to SSL 2.0 specs. from: Mozilla - SSL 2.0 Can I conclude that SSL 2.0 Finish messages does not provide AMC for all the messages sent/received by both parties (as in TLS 1.2)? Due to lack of SSL 2.0 official detailed documentation, I am unable to confirm this.

2.2.1 Assuming no session-identifier

client-hello         C -> S: challenge, cipher_specs
server-hello         S -> C: connection-id,server_certificate,cipher_specs
client-master-key    C -> S: {master_key}server_public_key
client-finish        C -> S: {connection-id}client_write_key
server-verify        S -> C: {challenge}server_write_key
server-finish        S -> C: {new_session_id}server_write_key
Source Link

SSL 2.0 Finished Message

Reference to SSL 2.0 specs. from: Mozilla - SSL 2.0 Can I conclude that SSL 2.0 Finish messages does not provide AMC for all the messages sent/received by both parties (as in TLS 1.2)? Due to lack of SSL 2.0 official detailed documentation, I am unable to confirm this.

2.2.1 Assuming no session-identifier

client-hello         C -> S: challenge, cipher_specs
server-hello         S -> C: connection-id,server_certificate,cipher_specs
client-master-key    C -> S: {master_key}server_public_key
client-finish        C -> S: {connection-id}client_write_key
server-verify        S -> C: {challenge}server_write_key
server-finish        S -> C: {new_session_id}server_write_key