When the RFC5246 was designed, why would the server verify the client's certificate by signing a client-key-Exchange message instead of explicitly requiring cert-verify message? For example, the algorithm suite ECDHE-RSA-* is in TLSv1.2.
In this process, the client-finished message also provides the cert-verify message to check the integrity of handshake messages?
Is the cert-verify message required? Regardless of existing compatibility issues.
@kaduk