Understanding 2048 bit SSL and 256 bit encryption

  • On DigiCert's page, they advertise a 2048 bit SSL with a 256 bit encryption: http://www.digicert.com/256-bit-ssl-certificates.htm

    What exactly is the difference here and why are two encryption bits being referenced?

    Here's a screenshot of the ad:

    On Geotrust's Premium SSL ad, they advertise it as:

    Security: domain control validation, strong 256-bit encryption, 2048-bit root

    So what's the difference between 256 bit encryption and 2048 bit root?

    Hope that clarifies the question.

    @Gilles: thanks for that link, but that's far too microscopic of an answer. I'm looking for an overview of what the difference is.

    Hmm I don't get why a certificate vendor talks about 256 bit encryption. The symmetric encryption used by SSL is completely independent from the certificate.

    @CodesInChaos: I agree, but maybe it is useful? Given the accepted answer below, my question is how would the client know to generate a random 256 bit key? (Why not 128?). If the server plays a role in the client's decision, then I can understand why the vendor would display this info.

    @Gilles I think that question is asking more about the bit encoding of keys, whereas I believe this one is about the difference between the types of keys.

    @Gilles, This question is from a "domain manager/user" POV.

  • The 2048-bit is about the RSA key pair: RSA keys are mathematical objects which include a big integer, and a "2048-bit key" is a key such that the big integer is larger than 22047 but smaller than 22048.

    The 256-bit is about SSL. In SSL, the server key is used only to transmit a random 256-bit key (that one does not have mathematical structure, it is just a bunch of bits); roughly speaking, the client generates a random 256-bit key, encrypts it with the server's RSA public key (the one which is in the server's certificate and is a "2048-bit key"), and sends the result to the server. The server uses its private RSA key to reverse the operation, and thus obtain the 256-bit key chosen by the client. Afterwards, client and server use the 256-bit to do symmetric encryption and integrity checks, and RSA is not used any further for that connection.

    See this answer for some more details. This setup is often called "hybrid encryption". This is done because RSA is not appropriate for bulk encryption, but symmetric encryption cannot do the initial public/private business which is needed to get things started.

    (SSL can do the key exchange with other algorithms than RSA so I have simplified description a bit in the text above, but that's the gist of the idea.)

    Thank you! Can you clarify this part: "the client generates a random 256-bit key"? In this case, the client is the browser? If so, does the ad mean to say that the root encryption is for the handshake portion and the 256 bit is for the data encryption? Hope I'm getting this.

    Ignore that question - I get it now. I combined your answer with the one in this post: http://security.stackexchange.com/questions/13688/my-understanding-of-how-https-works-gmail-for-example?lq=1 Thank you!

License under CC-BY-SA with attribution


Content dated before 6/26/2020 9:53 AM