For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Ken_B_50116's avatar
Ken_B_50116
Icon for Cirrostratus rankCirrostratus
Nov 04, 2015

Question about forcing TLS 1.2 and SOL13171

I found article SOL13171 that says to just use "TLSv1_2" in the Ciphers field, and this will force TLS 1.2. That sounds simple enough, but without also including "NATIVE" in the field, how can the encrypted connection even be established because nothing has been included to allow the other cipher suite protocols needed such as the bulk encryption algorithm, the key exchange, or any of that. I'm confused.

 

My goal is to force TLS 1.2 for Exchange 2010 clients.

 

6 Replies

  • What cipher string are you using now? There's a couple ways to accomplish this. You can change your cipher string or enable the

    No SSL, No TLSv1, and No TLSv1.1
    options in the Options List item in you client ssl profile. If your current cipher string id
    'DEFAULT'
    a simple change to
    'DEFAULT:!TLSv1:!TLSv1_1'
    would do the trick.

  • Currently the profile is just default.

    How is

    TLSv1_2
    functionally different than
    DEFAULT:!TLSv1:!TLSv1_1
    ? The SOL article says to use just
    TLSv1_2
    , but you suggestion makes more sense because it's starting with the default suites and then stripping out the bad TLS versions.

    • Brad_Parker's avatar
      Brad_Parker
      Icon for Cirrus rankCirrus
      Just TLSv1_2 on its own will also contain ADH, MD5, and RC4 ciphers which are all considered insecure at this point. The default string will not contain those. RC4 was remove from DEFAULT in 11.6 and ADH and MD5 removed in earlier versions.
    • Brad_Parker's avatar
      Brad_Parker
      Icon for Cirrus rankCirrus
      https://support.f5.com/kb/en-us/solutions/public/13000/100/sol13156.html
  • Here is a variant on my original question: I'm running 11.4.1 HF7. If I wanted to offer TLS 1.2 but not require it, then based on sol13156, most of the cipher suites include TLS 1.2 and a lower version. So at that point the version of TLS used depends on what the client tells the server it can support, and the LTM should use the most secure version?

     

    • Brad_Parker's avatar
      Brad_Parker
      Icon for Cirrus rankCirrus
      That is correct. The client sends its supported ciphers in the client Hello and the server, in this case the BigIP, will choose the cipher that matches highest in its list.