Devuan bug report logs - #270
unable to connect using TLSv1.2.

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: Thomas Groman <tgrom.automail@nuegia.net>
Subject: bug#270 closed by Mark Hindley <mark@hindley.org.uk> (Fixed in
 Debian #921151)
Message-ID: <handler.270.D270.16741546273686.notifdone@bugs.devuan.org>
References: <Y8mSazUMAgXhYMQL@hindley.org.uk>
 <154493212845.23324.11005533420082713814.reportbug@lappy>
X-Devuan-PR-Message: they-closed 270
X-Devuan-PR-Package: mariadb-client
X-Devuan-PR-Keywords: debian
Reply-To: 270@bugs.devuan.org
Date: Thu, 19 Jan 2023 18:58:03 +0000
Content-Type: multipart/mixed; boundary="----------=_1674154683-3694-1"

[Message part 1 (text/plain, inline)]

This is an automatic notification regarding your bug report
which was filed against the mariadb-client package:

#270: unable to connect using TLSv1.2.

It has been closed by Mark Hindley <mark@hindley.org.uk>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <mark@hindley.org.uk> by
replying to this email.


-- 
270: https://bugs.devuan.org/cgi/bugreport.cgi?bug=270
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mark Hindley <mark@hindley.org.uk>

To: 270-done@bugs.devuan.org

Subject: Fixed in Debian #921151

Date: Thu, 19 Jan 2023 18:56:43 +0000

Version:

[Message part 3 (message/rfc822, inline)]

From: Thomas Groman <tgrom.automail@nuegia.net>

To: Devuan Bug Tracking System <submit@bugs.devuan.org>

Subject: unable to connect using TLSv1.2.

Date: Sat, 15 Dec 2018 19:53:44 -0800

Package: mariadb-client
Version: 10.1.37-0+deb9u1
Severity: important



-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 2.0 (ascii)
Release:	2.0
Codename:	ascii

Architecture: x86_64

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages mariadb-client depends on:
ii  mariadb-client-10.1  10.1.37-0+deb9u1

mariadb-client recommends no packages.

mariadb-client suggests no packages.

-- no debconf information

Mariadb-client is unable to negotiate to TLSv1.2. I have tested this
with server versions: 10.1.37-MariaDB Gentoo Linux mariadb-10.1.37
10.1.34-MariaDB Gentoo Linux mariadb-10.1.34
. It should be noted that only the client version:
Ver 15.1 Distrib 10.1.37-MariaDB, for debian-linux-gnu (x86_64) using
readline 5.2 is unable to connect to the servers listed previously when
TLSv1.2 is enforced. However clients on other operating systems tested:
Ver 15.1 Distrib 10.1.34-MariaDB, for Linux (x86_64) using readline 7.0
Ver 15.1 Distrib 10.1.37-MariaDB, for Linux (x86_64) using readline 7.0
are able to connect just fine. Upon further inspection, looking at
packet traces with WireShark it appears that the Debian client is only
attempting to negotiate a connection with TLSv1.1, which is blacklisted
while the Gentoo clients are able to negotiate at TLSv1.2. The Debian
client fails and prints "ERROR 2026 (HY000): SSL connection error:
unknown error number" to stdout.

Send a report that this bug log contains spam.