X Certificate and Key Management

XCA supports MySQL, MariaDB and PostgreSQL as database server. This article shows briefly how to setup a database for XCA.

Prepare the XCA installation

Linux: Check whether the required package is installed: libqt5sql5-mysql libqt5sql5-psql Installing both is fine.

Setting up the database is as easy as:

  1. Create a database
  2. Create a user with full access to this database
  3. Setup network access permissions if required

The following examples assume:

  1. The database username as 'youruser'
  2. The database name as 'yourdbname'
  3. The password as 'yourpass'
  4. The Server IP as


Connect to your database as root:

$ sudo -u postgres psql

For remote access:

  1. Add the required "listen_addresses=localhost," in /etc/postgresql/9.1/main/postgresql.conf
  2. Enable the new user for remote access:
    $ sudo sh -c 'echo "host yourdbname youruser md5" >> /etc/postgresql/9.1/main/pg_hba.conf'
  3. Reload the server:
    $ sudo /etc/init.d/postgresql reload

MySQL / MariaDB

Connect to your database as root:

$ mysql -u root -p
GRANT ALL PRIVILEGES ON yourdbname.* to 'youruser'@'localhost' IDENTIFIED BY "yourpass";
GRANT ALL PRIVILEGES ON yourdbname.* to 'youruser'@'10.1.%' IDENTIFIED BY "yourpass"; -- For network access only

TLS Encrypted Database Connection

First of all you need certificates. A root ca and a server certificate with CN=hostname and SAN setup properly. Using XCA for this task is probably an option. Save them as cacert.pem, server-cert.pem and server-key.pem

PostgreSQL Server Configuration

Edit /etc/postgresql/9.6/main/pg_hba.conf and enforce SSL for user youruser

hostssl yourdbname youruser md5

Edit /etc/postgresql/9.6/main/pg_hba.conf and Enable TLS

ssl = true
ssl_prefer_server_ciphers = on
ssl_cert_file = '/etc/postgresql/9.6/main/server-cert.pem'
ssl_key_file = '/etc/postgresql/9.6/main/server-key.pem'
ssl_ca_file = '/etc/postgresql/9.6/main/cacert.pem'

and put the generated certificates in place.

XCA should already have saved the server-key.pem with permission 0600. Give postgres permission to the certificate and key:

chown postgres:postgres '/etc/postgresql/9.6/main/*.pem'

PostgreSQL Client Configuration

This configuration affects the pgsql connector, which is used by XCA. Symlink or copy the root CA certificate.

cp /etc/postgresql/9.6/main/cacert.pem ~/.postgresql/root.crt

On Windows the file location is


To verify the hostname during connection, start XCA with the environment variable PGSSLMODE=verify-full set:

PGSSLMODE=verify-full xca

More documentation on https://www.postgresql.org/docs/current/libpq-ssl.html

MariaDB Server Configuration

Edit the mariadb section in the file /etc/mysql/mariadb.conf.d/50-server.cnf:


Enforcing Encryption and rejectin unencrypted connections is documented here: https://mariadb.com/kb/en/securing-connections-for-client-and-server/

MariaDB Client Configuration

While the QT mySQL/MariaDB driver supports the configuration of SSL_CA certs I did not find a way to configure the ssl-verify-server-cert without patching the QT mySQL driver. If you know how, please tell me. Anyway, the connection is already encrypted with the server configuration above, but the server certificate is not verified and not protected against a MITM attack.

More documentation on https://mariadb.com/kb/en/securing-connections-for-client-and-server/

Importing an existing SQLite database

If you have an existing XCA file database, it can be imported, but only before the remote database is opened the first time. Using a table prefix is also not that easy currently. Export the .xdb file with:

$ sqlite3 your.xdb .dump > dump.sql

If the target database is MySQL or MariaDB, the dump.sql file must be modified. Delete the first 2 lines:

PRAGMA foreign_keys=OFF;

And add the line:


For PostgreSQL no modification is required. Insert the sql file via:

$ mysql -u xca -p xca < dump.sql
$ psql -h localhost xca xca < dump.sql

XCA Connection dialog

More than one XCA database in one remote database

The Table Prefix can be used to store more than one XCA database in the same remote database by using different table prefix settings.

Database passwords

When handling remote databases, there are 2 passwords. The first one for the database user 'youruser' (in this examples 'yourpass') to get permission to access the database server itself. XCA asks for it with:

"Please enter the password to access the database server as user 'youruser'."

The second one is the encryption/decryption password for the private keys stored inside the database. This is the password XCA also manages for SQLite databases

"Please enter the password for unlocking the database: youruser@"

This password is never transmitted over the network to the database server un-hashed. When using more than one XCA database in one server database only differing in the Table Prefix feature described above, the database server password for 'youruser' (in this examples 'yourpass') is the same for all those XCA databases. The password for encrypting and decrypting the private keys may be different for each.