Uploaded image for project: 'MariaDB Connector/C'
  1. MariaDB Connector/C
  2. CONC-567

Schannel - support TLSv1.3

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • None
    • 3.3.11
    • TLS/SSL
    • None

    Description

      Windows 10 and later , and Windows Server 2022, and later, support TLSv1.3
      How do they support them, is underdocumented, and so far many projects, e.g Curl , prefer to wait and see. Qt seems to implement 1.3 though already https://github.com/neverware-mirrors/qtbase/blob/dev/src/network/ssl/qsslsocket_schannel.cpp

      Attachments

        Issue Links

          is duplicated by

          Task - A task that needs to be done. CONC-653 TLS v1.3 support in Schannel

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28921 client on Windows doesn't support TLS 1.3

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CONC-639 Unable to connect to SSL using client certificates SEC_E_ALGORITHM_MISMATCH

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            Lotendan Lotendan added a comment -

            I have tested connecting to a MariaDB server with the help of MySQL C connector 8.4.0 and this seems to fix this issue.
            Maybe this helps?

            Lotendan Lotendan added a comment - I have tested connecting to a MariaDB server with the help of MySQL C connector 8.4.0 and this seems to fix this issue. Maybe this helps?
            RafaelKr Rafael Kraut added a comment -

            Also for reference: This was also fixed in HeidiSQL yesterday by using libmysql from MySQL 8.4.0 and there were some other minor changes required
            See https://github.com/HeidiSQL/HeidiSQL/issues/1768#issuecomment-2135832359

            RafaelKr Rafael Kraut added a comment - Also for reference: This was also fixed in HeidiSQL yesterday by using libmysql from MySQL 8.4.0 and there were some other minor changes required See https://github.com/HeidiSQL/HeidiSQL/issues/1768#issuecomment-2135832359
            wlad Vladislav Vaintroub added a comment - - edited

            Lotendan, RafaelKr , MySQL is using openssl everywhere, also on Windows, where openssl does not belong to system libraries. They had to change license for that. We did not do that (yet, and I'm not sure we'll ever do). So this is the reason TLSv1.3 is more painful to get working on Windows. On the server side, we can use WolfSSL, which is GPL2 comparible. On the client side, there is nothing on Windows, which would be LGPL2 compatible.

            That's to explain the difference between us and MySQL wrt client libraries,

            wlad Vladislav Vaintroub added a comment - - edited Lotendan , RafaelKr , MySQL is using openssl everywhere, also on Windows, where openssl does not belong to system libraries. They had to change license for that. We did not do that (yet, and I'm not sure we'll ever do). So this is the reason TLSv1.3 is more painful to get working on Windows. On the server side, we can use WolfSSL, which is GPL2 comparible. On the client side, there is nothing on Windows, which would be LGPL2 compatible. That's to explain the difference between us and MySQL wrt client libraries,

            People

              wlad Vladislav Vaintroub
              wlad Vladislav Vaintroub
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.