https://bugs.kde.org/show_bug.cgi?id=503894

--- Comment #21 from Karsten de Freese <[email protected]> ---
hi Chad,
have a look at 
https://mariadb.com/docs/server/security/securing-mariadb/securing-mariadb-encryption/data-in-transit-encryption/secure-connections-overview

Assuming you already have TLS certificates (e.g. from letsencrypt) set up on
the server that hosts the mariadb server, these are the steps that worked for
me:

 - on the server, locate the / a mariadb configuration file (there may be more
than one, which may all be evaluated)
   => in my case (under debian), I used '/etc/mysql/mariadb.cnf'
- look for the section '[mariadb]' (if there is none, create it by putting
[mariadb] at the beginning of an empty line)
- In this section (so it existed) you should find a few commented-out lines,
such as
  #ssl_cert = /etc/my.cnf.d/certificates/server-cert.pem
  #ssl_key = /etc/my.cnf.d/certificates/server-key.pem
  #ssl_ca = /etc/my.cnf.d/certificates/ca.pem
- Add the links to your existing TLS certificates - in my case these were
  ssl_cert = /etc/letsencrypt/live/<name of the server>/cert.pem
  ssl_key = /etc/letsencrypt/live/<name of the server>/privkey.pem
  => note that I have not added the link to the ca.pem - this should not be
needed for letsencrypt certificates
- now restart mariadb to evaluate the modified configuration using your OS'es
mechanism - in my case:
  sudo systemctl restart mariadb
- if you wish, you may check if TLS was actually enabled:
  - login to mariadb with your admin account: 
    sudo mariadb -u <admin name, e.g. root> -p
    => you will be prompted for your admin password
  - on the mariadb prompt, enter 
    SHOW GLOBAL VARIABLES LIKE 'have_ssl';  (the semicolon needs to be there)
- you should see something like 
+----------------------+-----------+
| Variable_name | Value    |
+----------------------+-----------+
| have_ssl            | YES       |
+----------------------+-----------+
- exit mariadb:
  exit;

That's it - digikam should now start, assuming that its databases had been
created correctly.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to