The Register Home Page

back to article Microsoft finally sends TLS 1.0 and 1.1 to the cloud retirement home

Today is the day Azure Storage stops supporting versions 1.0 and 1.1 of Transport Layer Security (TLS). TLS 1.2 is the new minimum. The change has been a long time coming. Microsoft warned users several years ago that February 3, 2026, was the cut-off date after which the deprecated standards would no longer be supported. The …

  1. Jou (Mxyzptlk) Silver badge

    Finally!

    I mean... TLS 1.2 with AES256 is there since Windows Vista! Why accept it in first place in Azure... MS should have done that over ten years ago.

    1. vapourEyz

      Re: Finally!

      Yup - 10 years sounds about right. It was that long ago that a client was upgraded from TLS1.1. Wow !

  2. cjcox

    How to take "your crappiness" and make it sound like genius

    On the client side Microsoft's love of old crap and "forever" keeping it... and now, saying "something".... sigh....

    Good to see.... but honestly, Microsoft has been in the trash bin due to this for a very very very very very very long time.

  3. david 12 Silver badge

    required manual tweaks to enable TLS 1.2.

    That is to say, one component of Windows 7 (schannel), required manual or scripted or policy or installation tweeking.

    I'm not aware of any version of Windows that supports 'thought control' (What You Want is What You Get), so in that sense any change you make to Windows default settings is "manual"

    1. Jou (Mxyzptlk) Silver badge

      Re: required manual tweaks to enable TLS 1.2.

      That requirement was removed somewhere around either Sp1 or Sp2. Not sure the exact date, but I know it definitely got removed, else I'd have nuked tons of them out of the network for more than a decade by enforcing it on Domain controllers and most other servers. Similar for Vista, same requirement was removed with Sp2 or shortly after.

  4. Throatwarbler Mangrove Silver badge
    Windows

    In fairness to Microsoft...

    As the article states, a big part of the problem is software which doesn't support the newer TLS protocols. At my old job, we had critical non-Microsoft software which had been developed well after 2008 but which for some reason didn't support TLS 1.2.

    1. Jou (Mxyzptlk) Silver badge

      Re: In fairness to Microsoft...

      Probably more a "uses that library in the product" effect than a conscious decision. That crypto stuff is ugly to manually take care of, let alone coding it. Which is the reason why wireguard became successful, removed a lot of unneeded complexity and nonsense bits...

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon