[TLS] Why does the client has to send a Certificate Verify while the server does not?

[ernuzwang at gmail.com]

Hi!

I've been reading RFCs concerning TLS and I have a question about Certificate Verify:

If I am not mistaken, Certificate Verify is a signature over the previous handshake messages using the client's private key, and the server 
verifies it with the client's public key, which can be extracted from the previous client certificate message. If it matches, the server is sure that 
the client actually owns the certificate (am I right?).

The above mechanism seems pretty secure to me, therefore, I'm wondering why the server is not required to send a verify as well? What if its 
certificate is eavesdropped or stolen and someone else can use it as its own since there is no way to verify if it does own it? (if it copies its 
domain name as well as its public key, etc.)
_______________________________________________
TLS mailing list
TLS at ietf.org
https://www.ietf.org/mailman/listinfo/tls