Gio.TlsDatabase

g GObject.Object GObject.Object Gio.TlsDatabase Gio.TlsDatabase GObject.Object->Gio.TlsDatabase

Subclasses:

None

Methods

Inherited:

GObject.Object (37)

Structs:

GObject.ObjectClass (5)

create_certificate_handle (certificate)

lookup_certificate_for_handle (handle, interaction, flags, cancellable)

lookup_certificate_for_handle_async (handle, interaction, flags, cancellable, callback, *user_data)

lookup_certificate_for_handle_finish (result)

lookup_certificate_issuer (certificate, interaction, flags, cancellable)

lookup_certificate_issuer_async (certificate, interaction, flags, cancellable, callback, *user_data)

lookup_certificate_issuer_finish (result)

lookup_certificates_issued_by (issuer_raw_dn, interaction, flags, cancellable)

lookup_certificates_issued_by_async (issuer_raw_dn, interaction, flags, cancellable, callback, *user_data)

lookup_certificates_issued_by_finish (result)

verify_chain (chain, purpose, identity, interaction, flags, cancellable)

verify_chain_async (chain, purpose, identity, interaction, flags, cancellable, callback, *user_data)

verify_chain_finish (result)

Virtual Methods

Inherited:

GObject.Object (7)

do_create_certificate_handle (certificate)

do_lookup_certificate_for_handle (handle, interaction, flags, cancellable)

do_lookup_certificate_for_handle_async (handle, interaction, flags, cancellable, callback, *user_data)

do_lookup_certificate_for_handle_finish (result)

do_lookup_certificate_issuer (certificate, interaction, flags, cancellable)

do_lookup_certificate_issuer_async (certificate, interaction, flags, cancellable, callback, *user_data)

do_lookup_certificate_issuer_finish (result)

do_lookup_certificates_issued_by (issuer_raw_dn, interaction, flags, cancellable)

do_lookup_certificates_issued_by_async (issuer_raw_dn, interaction, flags, cancellable, callback, *user_data)

do_lookup_certificates_issued_by_finish (result)

do_verify_chain (chain, purpose, identity, interaction, flags, cancellable)

do_verify_chain_async (chain, purpose, identity, interaction, flags, cancellable, callback, *user_data)

do_verify_chain_finish (result)

Properties

None

Signals

Inherited:

GObject.Object (1)

Fields

Inherited:

GObject.Object (1)

Name

Type

Access

Description

parent_instance

GObject.Object

r

Class Details

class Gio.TlsDatabase(**kwargs)
Bases:

GObject.Object

Abstract:

Yes

Structure:

Gio.TlsDatabaseClass

GTlsDatabase is used to look up certificates and other information from a certificate or key store. It is an abstract base class which TLS library specific subtypes override.

A GTlsDatabase may be accessed from multiple threads by the TLS backend. All implementations are required to be fully thread-safe.

Most common client applications will not directly interact with GTlsDatabase. It is used internally by [class`Gio`.TlsConnection].

New in version 2.30.

create_certificate_handle(certificate)[source]
Parameters:

certificate (Gio.TlsCertificate) – certificate for which to create a handle.

Returns:

a newly allocated string containing the handle.

Return type:

str or None

Create a handle string for the certificate. The database will only be able to create a handle for certificates that originate from the database. In cases where the database cannot create a handle for a certificate, None will be returned.

This handle should be stable across various instances of the application, and between applications. If a certificate is modified in the database, then it is not guaranteed that this handle will continue to point to it.

New in version 2.30.

lookup_certificate_for_handle(handle, interaction, flags, cancellable)[source]
Parameters:
Raises:

GLib.Error

Returns:

a newly allocated Gio.TlsCertificate, or None. Use GObject.Object.unref() to release the certificate.

Return type:

Gio.TlsCertificate or None

Look up a certificate by its handle.

The handle should have been created by calling Gio.TlsDatabase.create_certificate_handle() on a Gio.TlsDatabase object of the same TLS backend. The handle is designed to remain valid across instantiations of the database.

If the handle is no longer valid, or does not point to a certificate in this database, then None will be returned.

This function can block, use Gio.TlsDatabase.lookup_certificate_for_handle_async() to perform the lookup operation asynchronously.

New in version 2.30.

lookup_certificate_for_handle_async(handle, interaction, flags, cancellable, callback, *user_data)[source]
Parameters:

Asynchronously look up a certificate by its handle in the database. See Gio.TlsDatabase.lookup_certificate_for_handle() for more information.

New in version 2.30.

lookup_certificate_for_handle_finish(result)[source]
Parameters:

result (Gio.AsyncResult) – a Gio.AsyncResult.

Raises:

GLib.Error

Returns:

a newly allocated Gio.TlsCertificate object. Use GObject.Object.unref() to release the certificate.

Return type:

Gio.TlsCertificate

Finish an asynchronous lookup of a certificate by its handle. See Gio.TlsDatabase.lookup_certificate_for_handle() for more information.

If the handle is no longer valid, or does not point to a certificate in this database, then None will be returned.

New in version 2.30.

lookup_certificate_issuer(certificate, interaction, flags, cancellable)[source]
Parameters:
Raises:

GLib.Error

Returns:

a newly allocated issuer Gio.TlsCertificate, or None. Use GObject.Object.unref() to release the certificate.

Return type:

Gio.TlsCertificate

Look up the issuer of certificate in the database. The Gio.TlsCertificate :issuer property of certificate is not modified, and the two certificates are not hooked into a chain.

This function can block. Use Gio.TlsDatabase.lookup_certificate_issuer_async() to perform the lookup operation asynchronously.

Beware this function cannot be used to build certification paths. The issuer certificate returned by this function may not be the same as the certificate that would actually be used to construct a valid certification path during certificate verification. RFC 4158 explains why an issuer certificate cannot be naively assumed to be part of the the certification path (though GLib’s TLS backends may not follow the path building strategies outlined in this RFC). Due to the complexity of certification path building, GLib does not provide any way to know which certification path will actually be used when verifying a TLS certificate. Accordingly, this function cannot be used to make security-related decisions. Only GLib itself should make security decisions about TLS certificates.

New in version 2.30.

lookup_certificate_issuer_async(certificate, interaction, flags, cancellable, callback, *user_data)[source]
Parameters:

Asynchronously look up the issuer of certificate in the database. See Gio.TlsDatabase.lookup_certificate_issuer() for more information.

New in version 2.30.

lookup_certificate_issuer_finish(result)[source]
Parameters:

result (Gio.AsyncResult) – a Gio.AsyncResult.

Raises:

GLib.Error

Returns:

a newly allocated issuer Gio.TlsCertificate, or None. Use GObject.Object.unref() to release the certificate.

Return type:

Gio.TlsCertificate

Finish an asynchronous lookup issuer operation. See Gio.TlsDatabase.lookup_certificate_issuer() for more information.

New in version 2.30.

lookup_certificates_issued_by(issuer_raw_dn, interaction, flags, cancellable)[source]
Parameters:
Raises:

GLib.Error

Returns:

a newly allocated list of Gio.TlsCertificate objects. Use GObject.Object.unref() on each certificate, and g_list_free() on the release the list.

Return type:

[Gio.TlsCertificate]

Look up certificates issued by this issuer in the database.

This function can block, use Gio.TlsDatabase.lookup_certificates_issued_by_async() to perform the lookup operation asynchronously.

New in version 2.30.

lookup_certificates_issued_by_async(issuer_raw_dn, interaction, flags, cancellable, callback, *user_data)[source]
Parameters:

Asynchronously look up certificates issued by this issuer in the database. See Gio.TlsDatabase.lookup_certificates_issued_by() for more information.

The database may choose to hold a reference to the issuer byte array for the duration of this asynchronous operation. The byte array should not be modified during this time.

New in version 2.30.

lookup_certificates_issued_by_finish(result)[source]
Parameters:

result (Gio.AsyncResult) – a Gio.AsyncResult.

Raises:

GLib.Error

Returns:

a newly allocated list of Gio.TlsCertificate objects. Use GObject.Object.unref() on each certificate, and g_list_free() on the release the list.

Return type:

[Gio.TlsCertificate]

Finish an asynchronous lookup of certificates. See Gio.TlsDatabase.lookup_certificates_issued_by() for more information.

New in version 2.30.

verify_chain(chain, purpose, identity, interaction, flags, cancellable)[source]
Parameters:
Raises:

GLib.Error

Returns:

the appropriate Gio.TlsCertificateFlags which represents the result of verification.

Return type:

Gio.TlsCertificateFlags

Determines the validity of a certificate chain, outside the context of a TLS session.

chain is a chain of Gio.TlsCertificate objects each pointing to the next certificate in the chain by its Gio.TlsCertificate :issuer property.

purpose describes the purpose (or usage) for which the certificate is being used. Typically purpose will be set to Gio.TLS_DATABASE_PURPOSE_AUTHENTICATE_SERVER which means that the certificate is being used to authenticate a server (and we are acting as the client).

The identity is used to ensure the server certificate is valid for the expected peer identity. If the identity does not match the certificate, Gio.TlsCertificateFlags.BAD_IDENTITY will be set in the return value. If identity is None, that bit will never be set in the return value. The peer identity may also be used to check for pinned certificates (trust exceptions) in the database. These may override the normal verification process on a host-by-host basis.

Currently there are no flags, and Gio.TlsDatabaseVerifyFlags.NONE should be used.

If chain is found to be valid, then the return value will be 0. If chain is found to be invalid, then the return value will indicate at least one problem found. If the function is unable to determine whether chain is valid (for example, because cancellable is triggered before it completes) then the return value will be Gio.TlsCertificateFlags.GENERIC_ERROR and error will be set accordingly. error is not set when chain is successfully analyzed but found to be invalid.

GLib guarantees that if certificate verification fails, at least one error will be set in the return value, but it does not guarantee that all possible errors will be set. Accordingly, you may not safely decide to ignore any particular type of error. For example, it would be incorrect to mask Gio.TlsCertificateFlags.EXPIRED if you want to allow expired certificates, because this could potentially be the only error flag set even if other problems exist with the certificate.

Prior to GLib 2.48, GLib’s default TLS backend modified chain to represent the certification path built by Gio.TlsDatabase during certificate verification by adjusting the Gio.TlsCertificate :issuer property of each certificate in chain. Since GLib 2.48, this no longer occurs, so you cannot rely on Gio.TlsCertificate :issuer to represent the actual certification path used during certificate verification.

Because TLS session context is not used, Gio.TlsDatabase may not perform as many checks on the certificates as Gio.TlsConnection would. For example, certificate constraints may not be honored, and revocation checks may not be performed. The best way to verify TLS certificates used by a TLS connection is to let Gio.TlsConnection handle the verification.

The TLS backend may attempt to look up and add missing certificates to the chain. This may involve HTTP requests to download missing certificates.

This function can block. Use Gio.TlsDatabase.verify_chain_async() to perform the verification operation asynchronously.

New in version 2.30.

verify_chain_async(chain, purpose, identity, interaction, flags, cancellable, callback, *user_data)[source]
Parameters:

Asynchronously determines the validity of a certificate chain after looking up and adding any missing certificates to the chain. See Gio.TlsDatabase.verify_chain() for more information.

New in version 2.30.

verify_chain_finish(result)[source]
Parameters:

result (Gio.AsyncResult) – a Gio.AsyncResult.

Raises:

GLib.Error

Returns:

the appropriate Gio.TlsCertificateFlags which represents the result of verification.

Return type:

Gio.TlsCertificateFlags

Finish an asynchronous verify chain operation. See Gio.TlsDatabase.verify_chain() for more information.

If chain is found to be valid, then the return value will be 0. If chain is found to be invalid, then the return value will indicate the problems found. If the function is unable to determine whether chain is valid or not (eg, because cancellable is triggered before it completes) then the return value will be Gio.TlsCertificateFlags.GENERIC_ERROR and error will be set accordingly. error is not set when chain is successfully analyzed but found to be invalid.

New in version 2.30.

do_create_certificate_handle(certificate) virtual
Parameters:

certificate (Gio.TlsCertificate) – certificate for which to create a handle.

Returns:

a newly allocated string containing the handle.

Return type:

str or None

Create a handle string for the certificate. The database will only be able to create a handle for certificates that originate from the database. In cases where the database cannot create a handle for a certificate, None will be returned.

This handle should be stable across various instances of the application, and between applications. If a certificate is modified in the database, then it is not guaranteed that this handle will continue to point to it.

New in version 2.30.

do_lookup_certificate_for_handle(handle, interaction, flags, cancellable) virtual
Parameters:
Returns:

a newly allocated Gio.TlsCertificate, or None. Use GObject.Object.unref() to release the certificate.

Return type:

Gio.TlsCertificate or None

Look up a certificate by its handle.

The handle should have been created by calling Gio.TlsDatabase.create_certificate_handle() on a Gio.TlsDatabase object of the same TLS backend. The handle is designed to remain valid across instantiations of the database.

If the handle is no longer valid, or does not point to a certificate in this database, then None will be returned.

This function can block, use Gio.TlsDatabase.lookup_certificate_for_handle_async() to perform the lookup operation asynchronously.

New in version 2.30.

do_lookup_certificate_for_handle_async(handle, interaction, flags, cancellable, callback, *user_data) virtual
Parameters:

Asynchronously look up a certificate by its handle in the database. See Gio.TlsDatabase.lookup_certificate_for_handle() for more information.

New in version 2.30.

do_lookup_certificate_for_handle_finish(result) virtual
Parameters:

result (Gio.AsyncResult) – a Gio.AsyncResult.

Returns:

a newly allocated Gio.TlsCertificate object. Use GObject.Object.unref() to release the certificate.

Return type:

Gio.TlsCertificate

Finish an asynchronous lookup of a certificate by its handle. See Gio.TlsDatabase.lookup_certificate_for_handle() for more information.

If the handle is no longer valid, or does not point to a certificate in this database, then None will be returned.

New in version 2.30.

do_lookup_certificate_issuer(certificate, interaction, flags, cancellable) virtual
Parameters:
Returns:

a newly allocated issuer Gio.TlsCertificate, or None. Use GObject.Object.unref() to release the certificate.

Return type:

Gio.TlsCertificate

Look up the issuer of certificate in the database. The Gio.TlsCertificate :issuer property of certificate is not modified, and the two certificates are not hooked into a chain.

This function can block. Use Gio.TlsDatabase.lookup_certificate_issuer_async() to perform the lookup operation asynchronously.

Beware this function cannot be used to build certification paths. The issuer certificate returned by this function may not be the same as the certificate that would actually be used to construct a valid certification path during certificate verification. RFC 4158 explains why an issuer certificate cannot be naively assumed to be part of the the certification path (though GLib’s TLS backends may not follow the path building strategies outlined in this RFC). Due to the complexity of certification path building, GLib does not provide any way to know which certification path will actually be used when verifying a TLS certificate. Accordingly, this function cannot be used to make security-related decisions. Only GLib itself should make security decisions about TLS certificates.

New in version 2.30.

do_lookup_certificate_issuer_async(certificate, interaction, flags, cancellable, callback, *user_data) virtual
Parameters:

Asynchronously look up the issuer of certificate in the database. See Gio.TlsDatabase.lookup_certificate_issuer() for more information.

New in version 2.30.

do_lookup_certificate_issuer_finish(result) virtual
Parameters:

result (Gio.AsyncResult) – a Gio.AsyncResult.

Returns:

a newly allocated issuer Gio.TlsCertificate, or None. Use GObject.Object.unref() to release the certificate.

Return type:

Gio.TlsCertificate

Finish an asynchronous lookup issuer operation. See Gio.TlsDatabase.lookup_certificate_issuer() for more information.

New in version 2.30.

do_lookup_certificates_issued_by(issuer_raw_dn, interaction, flags, cancellable) virtual
Parameters:
Returns:

a newly allocated list of Gio.TlsCertificate objects. Use GObject.Object.unref() on each certificate, and g_list_free() on the release the list.

Return type:

[Gio.TlsCertificate]

Look up certificates issued by this issuer in the database.

This function can block, use Gio.TlsDatabase.lookup_certificates_issued_by_async() to perform the lookup operation asynchronously.

New in version 2.30.

do_lookup_certificates_issued_by_async(issuer_raw_dn, interaction, flags, cancellable, callback, *user_data) virtual
Parameters:

Asynchronously look up certificates issued by this issuer in the database. See Gio.TlsDatabase.lookup_certificates_issued_by() for more information.

The database may choose to hold a reference to the issuer byte array for the duration of this asynchronous operation. The byte array should not be modified during this time.

New in version 2.30.

do_lookup_certificates_issued_by_finish(result) virtual
Parameters:

result (Gio.AsyncResult) – a Gio.AsyncResult.

Returns:

a newly allocated list of Gio.TlsCertificate objects. Use GObject.Object.unref() on each certificate, and g_list_free() on the release the list.

Return type:

[Gio.TlsCertificate]

Finish an asynchronous lookup of certificates. See Gio.TlsDatabase.lookup_certificates_issued_by() for more information.

New in version 2.30.

do_verify_chain(chain, purpose, identity, interaction, flags, cancellable) virtual
Parameters:
Returns:

the appropriate Gio.TlsCertificateFlags which represents the result of verification.

Return type:

Gio.TlsCertificateFlags

Determines the validity of a certificate chain, outside the context of a TLS session.

chain is a chain of Gio.TlsCertificate objects each pointing to the next certificate in the chain by its Gio.TlsCertificate :issuer property.

purpose describes the purpose (or usage) for which the certificate is being used. Typically purpose will be set to Gio.TLS_DATABASE_PURPOSE_AUTHENTICATE_SERVER which means that the certificate is being used to authenticate a server (and we are acting as the client).

The identity is used to ensure the server certificate is valid for the expected peer identity. If the identity does not match the certificate, Gio.TlsCertificateFlags.BAD_IDENTITY will be set in the return value. If identity is None, that bit will never be set in the return value. The peer identity may also be used to check for pinned certificates (trust exceptions) in the database. These may override the normal verification process on a host-by-host basis.

Currently there are no flags, and Gio.TlsDatabaseVerifyFlags.NONE should be used.

If chain is found to be valid, then the return value will be 0. If chain is found to be invalid, then the return value will indicate at least one problem found. If the function is unable to determine whether chain is valid (for example, because cancellable is triggered before it completes) then the return value will be Gio.TlsCertificateFlags.GENERIC_ERROR and error will be set accordingly. error is not set when chain is successfully analyzed but found to be invalid.

GLib guarantees that if certificate verification fails, at least one error will be set in the return value, but it does not guarantee that all possible errors will be set. Accordingly, you may not safely decide to ignore any particular type of error. For example, it would be incorrect to mask Gio.TlsCertificateFlags.EXPIRED if you want to allow expired certificates, because this could potentially be the only error flag set even if other problems exist with the certificate.

Prior to GLib 2.48, GLib’s default TLS backend modified chain to represent the certification path built by Gio.TlsDatabase during certificate verification by adjusting the Gio.TlsCertificate :issuer property of each certificate in chain. Since GLib 2.48, this no longer occurs, so you cannot rely on Gio.TlsCertificate :issuer to represent the actual certification path used during certificate verification.

Because TLS session context is not used, Gio.TlsDatabase may not perform as many checks on the certificates as Gio.TlsConnection would. For example, certificate constraints may not be honored, and revocation checks may not be performed. The best way to verify TLS certificates used by a TLS connection is to let Gio.TlsConnection handle the verification.

The TLS backend may attempt to look up and add missing certificates to the chain. This may involve HTTP requests to download missing certificates.

This function can block. Use Gio.TlsDatabase.verify_chain_async() to perform the verification operation asynchronously.

New in version 2.30.

do_verify_chain_async(chain, purpose, identity, interaction, flags, cancellable, callback, *user_data) virtual
Parameters:

Asynchronously determines the validity of a certificate chain after looking up and adding any missing certificates to the chain. See Gio.TlsDatabase.verify_chain() for more information.

New in version 2.30.

do_verify_chain_finish(result) virtual
Parameters:

result (Gio.AsyncResult) – a Gio.AsyncResult.

Returns:

the appropriate Gio.TlsCertificateFlags which represents the result of verification.

Return type:

Gio.TlsCertificateFlags

Finish an asynchronous verify chain operation. See Gio.TlsDatabase.verify_chain() for more information.

If chain is found to be valid, then the return value will be 0. If chain is found to be invalid, then the return value will indicate the problems found. If the function is unable to determine whether chain is valid or not (eg, because cancellable is triggered before it completes) then the return value will be Gio.TlsCertificateFlags.GENERIC_ERROR and error will be set accordingly. error is not set when chain is successfully analyzed but found to be invalid.

New in version 2.30.