Re: [Proftpd-user] can't connect to mariadb database, when the user requires SSL after update from 1.3.9 to 1.3.9a

Hi,

On Fri, May 01, Preu=DFe, Hilmar via Proftp-user wrote:

> Am 30.04.2026 um 17:54 schrieb TJ Saunders:
> =

> Hello,
> =

> > When developing that patch to use the newer, non-deprecated APIs, I
> > verified locally against a MySQL database, using libmysqlclient, but
> > did not think to try using libmariadb and a MariaDB.  This
> > difference in behavior makes me wonder what the libmariadb
> > implementations, old and new, might look like.  I would have
> > expected that configuring the trusted CAs would (and should) have
> > been required from the beginning, regardless of the internal API
> > change in 1.3.9a.
> > =

> Thanks for explanation. So, what I understand it is quite unsure, why it
> happened now not earlier. Anyway I'll drop a note in the debian/NEWS file
> just any case anybody else runs into the issue. The OP did not mention a
> MariaDB change or something.

there was no change in the environment.
So it looks to me like the commit TJ mentioned caused the unexpected
behavior.

Till version 1.3.9 I didn't have to add the "ssl-ca:/etc/ssl/certs"
phrase to SQLConnectInfo

-- =

Regards

  Dieter

--
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
From field.


_______________________________________________
ProFTPD Users List   <[email protected]>
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html