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 -&gt; S: challenge, cipher_specs
server-hello         S -&gt; C: connection-id,server_certificate,cipher_specs
client-master-key    C -&gt; S: {master_key}server_public_key
client-finish        C -&gt; S: {connection-id}client_write_key
server-verify        S -&gt; C: {challenge}server_write_key
server-finish        S -&gt; C: {new_session_id}server_write_key
Yes, SSL2 did not MAC the handshake. See (recentish and more available) rfc6176 


  
  SSL 2.0 Deficiencies
  
  SSL version 2.0 [SSL2] deficiencies include the following:
  
  ...
  
  o  Handshake messages are not protected.  This permits a man-in-the-
    middle to trick the client into picking a weaker cipher suite than
    it would normally choose.