I know you can set the protocol/cipher via your web server:


ssl_protocols       TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers         HIGH:!aNULL:!MD5;


SSLProtocol all -SSLv2
SSLCipherSuite HIGH:!aNULL:!MD5

But my question is can a SSL Certificate be created to only work with certain protocols?

And can a certificate be created to only work with certain ciphers?

  • 3
    I very much doubt it, but there are so many nuances in those standards that if I post an answer that says "no, that's not possible" then someone is certain to be able to point to something in the spec that says I'm wrong... It's like how it never rains if you bring an umbrella. – a CVn Jul 13 '16 at 17:51
  • Your Apache config should -SSLv3. In addition to the answer (and my comment) below, nothing in the cert can control which SSL/TLS versions; however, an X.509 cert can and usually does use the ExtendedKeyUsage extension (EKU) to limit to SSL/TLS and not email (S/MIME) or vice versa, which is a 'certain' protocol but likely not the 'certain' protocol you wanted. – dave_thompson_085 Jul 14 '16 at 5:04
  • The question about the cipher is a duplicate of Can we restrict cipher suites using server certificate?. The question about the protocol not. – Steffen Ullrich Jul 14 '16 at 6:14

.. to only work with certain protocols? .. to only work with certain ciphers?

Certificates are mostly protocol independent.

But there is a slight correlation between certificate and cipher: one part of the cipher specifies the authentication algorithm and the possible algorithms depend on the kind of certificate. This means that you cannot use a RSA certificate with a *_ECDSA_* cipher and no ECDSA certificate with RSA key exchange. There are also ECDH (not ECDHE) and DH (not DHE) ciphers which require specific information in the certificate. But the choice of symmetric encryption (i.e. AES, RC4...) and the HMAC is independent from the certificate.

Which means the type of certificate limits which ciphers can be used but you cannot restrict the possible ciphers or protocols directly with some information in the certificate.

|improve this answer|||||

It would help if you think of the certificate based authentication or identify verification, separate from the integrity exchange, where the SSL ciphers really come in.

The certificate is only good for verifying the server "X" is really "X" and not "x".

The ciphers are, instead, used to provide a mechanism where you establish the symmetric key for data exchange. As you would guess, this phase would happen once the server authencity has been established.

|improve this answer|||||

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.