Skip to the content
mantichora_/docs

Encryption and certificates

Every server kind can be reached over TLS. The Encryption switch on the connection’s General tab has three positions, and only one of them checks who is answering.

The three modes

Off

Not encrypted: statements and rows cross the network as they are.

Encrypt

Encrypted, but the server’s certificate is not checked.

Encrypt and verify

Encrypted, and the server’s certificate is checked, host name included.

CautionEncrypt without verify protects against a listener, not against a server pretending to be yours.

Whose certificates are trusted

With Encrypt and verify, the CA file box appears. Leave it empty to trust the authorities this computer trusts. Choose a file with Choose a CA file to trust only the certificates in it: the way to reach a server whose certificate your own authority signed.

Over an SSH tunnel the certificate is checked against the host the connection names, which is the address the jump host dials, so the same check holds.

Where it applies

The switch is drawn for every server kind: PostgreSQL, MySQL, SQL Server, Oracle, ClickHouse, Snowflake, MongoDB, Redis, Cassandra, Arrow Flight SQL, Trino, Elasticsearch and SAP HANA. SQLite and DuckDB are files, with nothing to encrypt.

An ODBC connection is encrypted by its driver: say so in the DSN or the connection string, Encrypt=yes for SQL Server’s driver or SSLmode=verify-full for PostgreSQL’s.

NoteElasticsearch, Trino, Arrow Flight SQL and Snowflake keep the scheme of their host: one written with https:// or grpc+tls:// is encrypted even with the switch off, against this computer’s authorities, and so is a bare Snowflake host. A client certificate cannot be given: the window signs in with the user and the password.