Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Microsoft remove TLS 1.0 and TLS 1.1 from Windows 11
QtWS25 Last Chance

Microsoft remove TLS 1.0 and TLS 1.1 from Windows 11

Scheduled Pinned Locked Moved Unsolved General and Desktop
3 Posts 2 Posters 317 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • piervalliP Do not disturb
    piervalliP Do not disturb
    piervalli
    wrote on last edited by
    #1

    Hi,
    Microsoft remove TLS 1.0 and TLS 1.1 from WIndows 11
    this is a link of Microsoft

    https://techcommunity.microsoft.com/t5/windows-it-pro-blog/tls-1-0-and-tls-1-1-soon-to-be-disabled-in-windows/ba-p/3887947

    Should be a problem for Qt 5.15?
    Thanks

    kkoehneK 1 Reply Last reply
    0
    • piervalliP piervalli

      Hi,
      Microsoft remove TLS 1.0 and TLS 1.1 from WIndows 11
      this is a link of Microsoft

      https://techcommunity.microsoft.com/t5/windows-it-pro-blog/tls-1-0-and-tls-1-1-soon-to-be-disabled-in-windows/ba-p/3887947

      Should be a problem for Qt 5.15?
      Thanks

      kkoehneK Offline
      kkoehneK Offline
      kkoehne
      Moderators
      wrote on last edited by
      #2

      @piervalli Interesting!

      As Qt 5 binaries by default use openssl and not TLS, this should not have any impact on Qt 5.15. That is, unless you configured Qt yourself and explicitly added -schannel.

      For Qt 6.2 onwards, Qt is by default built both with OpenSSL and schannel support. Anyhow, Qt doesn't hardcode any ciphers on it's own, but relies on the system defaults. So this should be only a problem if you're relying on schannel to connect to a server that doesn't support anything but TLS 1.0 or TLS 1.1, or have hardcoded your app to use TLS 1.0 or TLS 1.1 (for instance by calling QSslConfiguration::setProtocol()).

      Director R&D, The Qt Company

      piervalliP 1 Reply Last reply
      2
      • kkoehneK kkoehne

        @piervalli Interesting!

        As Qt 5 binaries by default use openssl and not TLS, this should not have any impact on Qt 5.15. That is, unless you configured Qt yourself and explicitly added -schannel.

        For Qt 6.2 onwards, Qt is by default built both with OpenSSL and schannel support. Anyhow, Qt doesn't hardcode any ciphers on it's own, but relies on the system defaults. So this should be only a problem if you're relying on schannel to connect to a server that doesn't support anything but TLS 1.0 or TLS 1.1, or have hardcoded your app to use TLS 1.0 or TLS 1.1 (for instance by calling QSslConfiguration::setProtocol()).

        piervalliP Do not disturb
        piervalliP Do not disturb
        piervalli
        wrote on last edited by
        #3

        @kkoehne
        Thanks

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved