Gio.TlsConnection:database
Description: Reference for property Gio.TlsConnection:database

### Property

# Gio TlsConnection:database

since: 2.30

#### Declaration

    property database: Gio.TlsDatabase [ read, write ]

#### Description [src]

The certificate database to use when verifying this TLS connection. If no certificate database is set, then the default database will be used. See g_tls_backend_get_default_database().

When using a non-default database, `GTlsConnection` must fall back to using the `GTlsDatabase` to perform certificate verification using g_tls_database_verify_chain(), which means certificate verification will not be able to make use of TLS session context. This may be less secure. For example, if you create your own `GTlsDatabase` that just wraps the default `GTlsDatabase`, you might expect that you have not changed anything, but this is not true because you may have altered the behavior of `GTlsConnection` by causing it to use g_tls_database_verify_chain(). See the documentation of `g_tls_database_verify_chain()` for more details on specific security checks that may not be performed. Accordingly, setting a non-default database is discouraged except for specialty applications with unusual security requirements.

Type:`GTlsDatabase`

Available since: 2.30

Getter method | `g_tls_connection_get_database()`
Setter method | `g_tls_connection_set_database()`

#### Flags

Readable | yes
Writable | yes
Construct | no
Construct only | no