Ansgar Becker

Related: #22 Do you have a suggestion how to fix this? I'm not that deep into PostgreSQL.

Your password likely contains characters which get broken through my obfuscation logic used when storing it in your registry. Reading out such a broken password results in a wrong password,...

Please try the other libraries as well. The issue may be caused by libmariadb.dll. And of course retry with the latest v12.5.

Here's a comment saying the error is only present in the 32bit version of HeidiSQL, but not in the 64bit builds: https://aur.archlinux.org/packages/heidisql#comment-889051 . Can you confirm that?

Thanks for your tests and research. According to the documentation of [mysql_ssl_set](https://mariadb.com/kb/en/mysql_ssl_set/) (which HeidiSQL uses), the CA file is passed correctly to the library. One cause could be that the...

This may be related to what I found recently, and which also caused issue #1426 . If you update HeidiSQL with the latest build installer from the nightly builds page,...

Will have to test this myself, with a passphrased key. I suspect my code for reading the plink output is again buggy.

In 51da7c8efc890ebdb394dfa53f911b64223a53e8 I already told libmariadb/libmysql to support TLS versions up to 1.3. Did you already try the different libraries for it? I recommend libmariadb.dll, but please also try the...

@tqre-mc please retry with the next (soon coming) release v12.7 with updated libmariadb.dll. I just updated it for #1946 .

@batteryf1 or @bst-biwac or someone: could you please test with the next build (6831). I believe the shown "wrong passphrase" dialog is just shown in the wrong order, which should...