This will never be fixed for MariaDB 10.3, but is has been fixed for MariaDB 10.5 since it was allowed to use OpenSSL in Debian: https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/ca2574aa88434d1c49456c677b7dcb904902daaf
And we are even automatically testing SSL connections in Salsa-CI: https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/23376b43714be4dbb53782b3ef1fa7b7eff24daf ** Changed in: mariadb-10.3 (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: mariadb-10.5 (Ubuntu) Importance: Undecided Status: New ** Changed in: mariadb-10.5 (Ubuntu) Status: New => Fix Released ** Changed in: mariadb-10.5 (Ubuntu) Assignee: (unassigned) => Otto Kekäläinen (otto) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885632 Title: Ubuntu 20.04 requires TLSv1.2 while MariaDB 10.3/YaSSL only supports max TLSv1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1885632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
