Finding the answers to specific SSL questions

Finding the answers to specific SSL questions

I have a couple questions about SSL. First of all, why does SSL have a Change Cipher Spec Protocol that contains only the change_cipher_spec message? Why was the change_cipher_spec message just not defined in the Handshake Protocol? I'm sure there is a reason that a separate protocol was created, but I have not been able to find it.

My second question is about the client and server secrets and keys in the connection state. Why are there two write MAC secrets (one for the client and one for the server) and two write keys (one for the client and one for the server) in the connection state? I can understand why one MAC secret and one write key would be needed, but I can't understand why there are two of each. Aren't these secrets and keys symmetric, meaning only one key/secret is needed?

Any help you could give me on this would be greatly appreciated.


    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The best place to find the answers to your questions would be the SSL/TLS working group mailing lists in the IETF. Many questions -- like "why did you do it this way" are best answered by the people who actually did it. Here is information about the working group mailing lists:

General Discussion: ietf-tls@lists.certicom.com
To Subscribe: ietf-tls-request@lists.certicom.com
Archive: http://www.imc.org/ietf-tls/mail-archive


This was first published in September 2002