Skip to content

Gio.DtlsConnection

interface

GDtlsConnection is the base DTLS connection class type, which wraps a DatagramBased and provides DTLS encryption on top of it. Its subclasses, DtlsClientConnection and DtlsServerConnection, implement client-side and server-side DTLS, respectively.

For TLS support, see TlsConnection.

As DTLS is datagram based, GDtlsConnection implements DatagramBased, presenting a datagram-socket-like API for the encrypted connection. This operates over a base datagram connection, which is also a GDatagramBased (DtlsConnection.base-socket).

To close a DTLS connection, use DtlsConnection.close.

Neither DtlsServerConnection or DtlsClientConnection set the peer address on their base DatagramBased if it is a Socket — it is up to the caller to do that if they wish. If they do not, and Socket.close is called on the base socket, the GDtlsConnection will not raise a G_IO_ERROR_NOT_CONNECTED error on further I/O.

Methods

close

def close(self, cancellable: Cancellable | None = ...) -> bool

Close the DTLS connection. This is equivalent to calling DtlsConnection.shutdown to shut down both sides of the connection.

Closing a DtlsConnection waits for all buffered but untransmitted data to be sent before it completes. It then sends a close_notify DTLS alert to the peer and may wait for a close_notify to be received from the peer. It does not close the underlying DtlsConnection:base-socket; that must be closed separately.

Once conn is closed, all other operations will return IOErrorEnum.CLOSED. Closing a DtlsConnection multiple times will not return an error.

GDtlsConnections will be automatically closed when the last reference is dropped, but you might want to call this function to make sure resources are released as early as possible.

If cancellable is cancelled, the DtlsConnection may be left partially-closed and any pending untransmitted data may be lost. Call DtlsConnection.close again to complete closing the DtlsConnection.

Parameters:

close_async

def close_async(self, io_priority: int, cancellable: Cancellable | None = ..., callback: Callable[[DtlsConnection | None, AsyncResult], None] | None = ...) -> None

Asynchronously close the DTLS connection. See DtlsConnection.close for more information.

Parameters:

  • io_priority — the I/O priority of the request
  • cancellable — a Cancellable, or None
  • callback — callback to call when the close operation is complete

close_finish

def close_finish(self, result: AsyncResult) -> bool

Finish an asynchronous TLS close operation. See DtlsConnection.close for more information.

Parameters:

emit_accept_certificate

def emit_accept_certificate(self, peer_cert: TlsCertificate, errors: TlsCertificateFlags | int) -> bool

Used by DtlsConnection implementations to emit the DtlsConnection::accept-certificate signal.

Parameters:

  • peer_cert — the peer's TlsCertificate
  • errors — the problems with peer_cert

get_certificate

def get_certificate(self) -> TlsCertificate | None

Gets conn's certificate, as set by DtlsConnection.set_certificate.

get_channel_binding_data

def get_channel_binding_data(self, type: TlsChannelBindingType | int) -> tuple[bool, list[int]]

Query the TLS backend for TLS channel binding data of type for conn.

This call retrieves TLS channel binding data as specified in RFC 5056, RFC 5929, and related RFCs. The binding data is returned in data. The data is resized by the callee using GLib.ByteArray buffer management and will be freed when the data is destroyed by GLib.ByteArray.unref. If data is None, it will only check whether TLS backend is able to fetch the data (e.g. whether type is supported by the TLS backend). It does not guarantee that the data will be available though. That could happen if TLS connection does not support type or the binding data is not available yet due to additional negotiation or input required.

Parameters:

get_ciphersuite_name

def get_ciphersuite_name(self) -> str | None

Returns the name of the current DTLS ciphersuite, or None if the connection has not handshaked or has been closed. Beware that the TLS backend may use any of multiple different naming conventions, because OpenSSL and GnuTLS have their own ciphersuite naming conventions that are different from each other and different from the standard, IANA- registered ciphersuite names. The ciphersuite name is intended to be displayed to the user for informative purposes only, and parsing it is not recommended.

get_database

def get_database(self) -> TlsDatabase | None

Gets the certificate database that conn uses to verify peer certificates. See DtlsConnection.set_database.

get_interaction

def get_interaction(self) -> TlsInteraction | None

Get the object that will be used to interact with the user. It will be used for things like prompting the user for passwords. If None is returned, then no user interaction will occur for this connection.

get_negotiated_protocol

def get_negotiated_protocol(self) -> str | None

Gets the name of the application-layer protocol negotiated during the handshake.

If the peer did not use the ALPN extension, or did not advertise a protocol that matched one of conn's protocols, or the TLS backend does not support ALPN, then this will be None. See DtlsConnection.set_advertised_protocols.

get_peer_certificate

def get_peer_certificate(self) -> TlsCertificate | None

Gets conn's peer's certificate after the handshake has completed or failed. (It is not set during the emission of DtlsConnection::accept-certificate.)

get_peer_certificate_errors

def get_peer_certificate_errors(self) -> TlsCertificateFlags

Gets the errors associated with validating conn's peer's certificate, after the handshake has completed or failed. (It is not set during the emission of DtlsConnection::accept-certificate.)

get_protocol_version

def get_protocol_version(self) -> TlsProtocolVersion

Returns the current DTLS protocol version, which may be TlsProtocolVersion.UNKNOWN if the connection has not handshaked, or has been closed, or if the TLS backend has implemented a protocol version that is not a recognized TlsProtocolVersion.

get_rehandshake_mode

def get_rehandshake_mode(self) -> TlsRehandshakeMode

:::warning Deprecated since 2.64. This API is deprecated. :::

Gets conn rehandshaking mode. See DtlsConnection.set_rehandshake_mode for details.

get_require_close_notify

def get_require_close_notify(self) -> bool

Tests whether or not conn expects a proper TLS close notification when the connection is closed. See DtlsConnection.set_require_close_notify for details.

handshake

def handshake(self, cancellable: Cancellable | None = ...) -> bool

Attempts a TLS handshake on conn.

On the client side, it is never necessary to call this method; although the connection needs to perform a handshake after connecting, DtlsConnection will handle this for you automatically when you try to send or receive data on the connection. You can call DtlsConnection.handshake manually if you want to know whether the initial handshake succeeded or failed (as opposed to just immediately trying to use conn to read or write, in which case, if it fails, it may not be possible to tell if it failed before or after completing the handshake), but beware that servers may reject client authentication after the handshake has completed, so a successful handshake does not indicate the connection will be usable.

Likewise, on the server side, although a handshake is necessary at the beginning of the communication, you do not need to call this function explicitly unless you want clearer error reporting.

Previously, calling DtlsConnection.handshake after the initial handshake would trigger a rehandshake; however, this usage was deprecated in GLib 2.60 because rehandshaking was removed from the TLS protocol in TLS 1.3. Since GLib 2.64, calling this function after the initial handshake will no longer do anything.

DtlsConnection::accept_certificate may be emitted during the handshake.

Parameters:

handshake_async

def handshake_async(self, io_priority: int, cancellable: Cancellable | None = ..., callback: Callable[[DtlsConnection | None, AsyncResult], None] | None = ...) -> None

Asynchronously performs a TLS handshake on conn. See DtlsConnection.handshake for more information.

Parameters:

  • io_priority — the I/O priority of the request
  • cancellable — a Cancellable, or None
  • callback — callback to call when the handshake is complete

handshake_finish

def handshake_finish(self, result: AsyncResult) -> bool

Finish an asynchronous TLS handshake operation. See DtlsConnection.handshake for more information.

Parameters:

set_advertised_protocols

def set_advertised_protocols(self, protocols: list[str] | None = ...) -> None

Sets the list of application-layer protocols to advertise that the caller is willing to speak on this connection. The Application-Layer Protocol Negotiation (ALPN) extension will be used to negotiate a compatible protocol with the peer; use DtlsConnection.get_negotiated_protocol to find the negotiated protocol after the handshake. Specifying None for the the value of protocols will disable ALPN negotiation.

See IANA TLS ALPN Protocol IDs for a list of registered protocol IDs.

Parameters:

  • protocols — a None-terminated array of ALPN protocol names (eg, "http/1.1", "h2"), or None

set_certificate

def set_certificate(self, certificate: TlsCertificate) -> None

This sets the certificate that conn will present to its peer during the TLS handshake. For a DtlsServerConnection, it is mandatory to set this, and that will normally be done at construct time.

For a DtlsClientConnection, this is optional. If a handshake fails with TlsError.CERTIFICATE_REQUIRED, that means that the server requires a certificate, and if you try connecting again, you should call this method first. You can call DtlsClientConnection.get_accepted_cas on the failed connection to get a list of Certificate Authorities that the server will accept certificates from.

(It is also possible that a server will allow the connection with or without a certificate; in that case, if you don't provide a certificate, you can tell that the server requested one by the fact that DtlsClientConnection.get_accepted_cas will return non-None.)

Parameters:

  • certificate — the certificate to use for conn

set_database

def set_database(self, database: TlsDatabase | None = ...) -> None

Sets the certificate database that is used to verify peer certificates. This is set to the default database by default. See TlsBackend.get_default_database. If set to None, then peer certificate validation will always set the TlsCertificateFlags.UNKNOWN_CA error (meaning DtlsConnection::accept-certificate will always be emitted on client-side connections, unless that bit is not set in DtlsClientConnection:validation-flags).

There are nonintuitive security implications when using a non-default database. See DtlsConnection:database for details.

Parameters:

set_interaction

def set_interaction(self, interaction: TlsInteraction | None = ...) -> None

Set the object that will be used to interact with the user. It will be used for things like prompting the user for passwords.

The interaction argument will normally be a derived subclass of TlsInteraction. None can also be provided if no user interaction should occur for this connection.

Parameters:

  • interaction — an interaction object, or None

set_rehandshake_mode

def set_rehandshake_mode(self, mode: TlsRehandshakeMode | int) -> None

:::warning Deprecated since 2.60. This API is deprecated. :::

Since GLib 2.64, changing the rehandshake mode is no longer supported and will have no effect. With TLS 1.3, rehandshaking has been removed from the TLS protocol, replaced by separate post-handshake authentication and rekey operations.

Parameters:

  • mode — the rehandshaking mode

set_require_close_notify

def set_require_close_notify(self, require_close_notify: bool) -> None

Sets whether or not conn expects a proper TLS close notification before the connection is closed. If this is True (the default), then conn will expect to receive a TLS close notification from its peer before the connection is closed, and will return a TlsError.EOF error if the connection is closed without proper notification (since this may indicate a network error, or man-in-the-middle attack).

In some protocols, the application will know whether or not the connection was closed cleanly based on application-level data (because the application-level data includes a length field, or is somehow self-delimiting); in this case, the close notify is redundant and may be omitted. You can use DtlsConnection.set_require_close_notify to tell conn to allow an "unannounced" connection close, in which case the close will show up as a 0-length read, as in a non-TLS DatagramBased, and it is up to the application to check that the data has been fully received.

Note that this only affects the behavior when the peer closes the connection; when the application calls DtlsConnection.close_async on conn itself, this will send a close notification regardless of the setting of this property. If you explicitly want to do an unclean close, you can close conn's DtlsConnection:base-socket rather than closing conn itself.

Parameters:

  • require_close_notify — whether or not to require close notification

shutdown

def shutdown(self, shutdown_read: bool, shutdown_write: bool, cancellable: Cancellable | None = ...) -> bool

Shut down part or all of a DTLS connection.

If shutdown_read is True then the receiving side of the connection is shut down, and further reading is disallowed. Subsequent calls to DatagramBased.receive_messages will return IOErrorEnum.CLOSED.

If shutdown_write is True then the sending side of the connection is shut down, and further writing is disallowed. Subsequent calls to DatagramBased.send_messages will return IOErrorEnum.CLOSED.

It is allowed for both shutdown_read and shutdown_write to be TRUE — this is equivalent to calling DtlsConnection.close.

If cancellable is cancelled, the DtlsConnection may be left partially-closed and any pending untransmitted data may be lost. Call DtlsConnection.shutdown again to complete closing the DtlsConnection.

Parameters:

  • shutdown_read — True to stop reception of incoming datagrams
  • shutdown_write — True to stop sending outgoing datagrams
  • cancellable — a Cancellable, or None

shutdown_async

def shutdown_async(self, shutdown_read: bool, shutdown_write: bool, io_priority: int, cancellable: Cancellable | None = ..., callback: Callable[[DtlsConnection | None, AsyncResult], None] | None = ...) -> None

Asynchronously shut down part or all of the DTLS connection. See DtlsConnection.shutdown for more information.

Parameters:

  • shutdown_read — True to stop reception of incoming datagrams
  • shutdown_write — True to stop sending outgoing datagrams
  • io_priority — the I/O priority of the request
  • cancellable — a Cancellable, or None
  • callback — callback to call when the shutdown operation is complete

shutdown_finish

def shutdown_finish(self, result: AsyncResult) -> bool

Finish an asynchronous TLS shutdown operation. See DtlsConnection.shutdown for more information.

Parameters:

Virtual methods

do_accept_certificate

def do_accept_certificate(self, peer_cert: TlsCertificate, errors: TlsCertificateFlags | int) -> bool

Check whether to accept a certificate.

do_get_binding_data

def do_get_binding_data(self, type: TlsChannelBindingType | int, data: list[int]) -> bool

Retrieve TLS channel binding data (Since: 2.66)

do_get_negotiated_protocol

def do_get_negotiated_protocol(self) -> str | None

Gets the name of the application-layer protocol negotiated during the handshake.

If the peer did not use the ALPN extension, or did not advertise a protocol that matched one of conn's protocols, or the TLS backend does not support ALPN, then this will be None. See DtlsConnection.set_advertised_protocols.

do_handshake

def do_handshake(self, cancellable: Cancellable | None = ...) -> bool

Attempts a TLS handshake on conn.

On the client side, it is never necessary to call this method; although the connection needs to perform a handshake after connecting, DtlsConnection will handle this for you automatically when you try to send or receive data on the connection. You can call DtlsConnection.handshake manually if you want to know whether the initial handshake succeeded or failed (as opposed to just immediately trying to use conn to read or write, in which case, if it fails, it may not be possible to tell if it failed before or after completing the handshake), but beware that servers may reject client authentication after the handshake has completed, so a successful handshake does not indicate the connection will be usable.

Likewise, on the server side, although a handshake is necessary at the beginning of the communication, you do not need to call this function explicitly unless you want clearer error reporting.

Previously, calling DtlsConnection.handshake after the initial handshake would trigger a rehandshake; however, this usage was deprecated in GLib 2.60 because rehandshaking was removed from the TLS protocol in TLS 1.3. Since GLib 2.64, calling this function after the initial handshake will no longer do anything.

DtlsConnection::accept_certificate may be emitted during the handshake.

Parameters:

do_handshake_async

def do_handshake_async(self, io_priority: int, cancellable: Cancellable | None = ..., callback: Callable[[DtlsConnection | None, AsyncResult], None] | None = ...) -> None

Asynchronously performs a TLS handshake on conn. See DtlsConnection.handshake for more information.

Parameters:

  • io_priority — the I/O priority of the request
  • cancellable — a Cancellable, or None
  • callback — callback to call when the handshake is complete

do_handshake_finish

def do_handshake_finish(self, result: AsyncResult) -> bool

Finish an asynchronous TLS handshake operation. See DtlsConnection.handshake for more information.

Parameters:

do_set_advertised_protocols

def do_set_advertised_protocols(self, protocols: list[str] | None = ...) -> None

Sets the list of application-layer protocols to advertise that the caller is willing to speak on this connection. The Application-Layer Protocol Negotiation (ALPN) extension will be used to negotiate a compatible protocol with the peer; use DtlsConnection.get_negotiated_protocol to find the negotiated protocol after the handshake. Specifying None for the the value of protocols will disable ALPN negotiation.

See IANA TLS ALPN Protocol IDs for a list of registered protocol IDs.

Parameters:

  • protocols — a None-terminated array of ALPN protocol names (eg, "http/1.1", "h2"), or None

do_shutdown

def do_shutdown(self, shutdown_read: bool, shutdown_write: bool, cancellable: Cancellable | None = ...) -> bool

Shut down part or all of a DTLS connection.

If shutdown_read is True then the receiving side of the connection is shut down, and further reading is disallowed. Subsequent calls to DatagramBased.receive_messages will return IOErrorEnum.CLOSED.

If shutdown_write is True then the sending side of the connection is shut down, and further writing is disallowed. Subsequent calls to DatagramBased.send_messages will return IOErrorEnum.CLOSED.

It is allowed for both shutdown_read and shutdown_write to be TRUE — this is equivalent to calling DtlsConnection.close.

If cancellable is cancelled, the DtlsConnection may be left partially-closed and any pending untransmitted data may be lost. Call DtlsConnection.shutdown again to complete closing the DtlsConnection.

Parameters:

  • shutdown_read — True to stop reception of incoming datagrams
  • shutdown_write — True to stop sending outgoing datagrams
  • cancellable — a Cancellable, or None

do_shutdown_async

def do_shutdown_async(self, shutdown_read: bool, shutdown_write: bool, io_priority: int, cancellable: Cancellable | None = ..., callback: Callable[[DtlsConnection | None, AsyncResult], None] | None = ...) -> None

Asynchronously shut down part or all of the DTLS connection. See DtlsConnection.shutdown for more information.

Parameters:

  • shutdown_read — True to stop reception of incoming datagrams
  • shutdown_write — True to stop sending outgoing datagrams
  • io_priority — the I/O priority of the request
  • cancellable — a Cancellable, or None
  • callback — callback to call when the shutdown operation is complete

do_shutdown_finish

def do_shutdown_finish(self, result: AsyncResult) -> bool

Finish an asynchronous TLS shutdown operation. See DtlsConnection.shutdown for more information.

Parameters:

Properties

advertised_protocols

advertised_protocols: list[str]  # read/write

The list of application-layer protocols that the connection advertises that it is willing to speak. See DtlsConnection.set_advertised_protocols.

base_socket

base_socket: DatagramBased  # read/write

The DatagramBased that the connection wraps. Note that this may be any implementation of DatagramBased, not just a Socket.

certificate

certificate: TlsCertificate  # read/write

The connection's certificate; see DtlsConnection.set_certificate.

ciphersuite_name

ciphersuite_name: str  # read-only

The name of the DTLS ciphersuite in use. See DtlsConnection.get_ciphersuite_name.

database

database: TlsDatabase  # read/write

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

When using a non-default database, DtlsConnection must fall back to using the TlsDatabase to perform certificate verification using TlsDatabase.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 TlsDatabase that just wraps the default TlsDatabase, you might expect that you have not changed anything, but this is not true because you may have altered the behavior of DtlsConnection by causing it to use TlsDatabase.verify_chain. See the documentation of TlsDatabase.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.

interaction

interaction: TlsInteraction  # read/write

A TlsInteraction object to be used when the connection or certificate database need to interact with the user. This will be used to prompt the user for passwords where necessary.

negotiated_protocol

negotiated_protocol: str  # read-only

The application-layer protocol negotiated during the TLS handshake. See DtlsConnection.get_negotiated_protocol.

peer_certificate

peer_certificate: TlsCertificate  # read-only

The connection's peer's certificate, after the TLS handshake has completed or failed. Note in particular that this is not yet set during the emission of DtlsConnection::accept-certificate.

(You can watch for a GObject.Object::notify signal on this property to detect when a handshake has occurred.)

peer_certificate_errors

peer_certificate_errors: TlsCertificateFlags | int  # read-only

The errors noticed while verifying DtlsConnection:peer-certificate. Normally this should be 0, but it may not be if DtlsClientConnection:validation-flags is not TlsCertificateFlags.VALIDATE_ALL, or if DtlsConnection::accept-certificate overrode the default behavior.

GLib guarantees that if certificate verification fails, at least one error will be set, 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 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.

protocol_version

protocol_version: TlsProtocolVersion | int  # read-only

The DTLS protocol version in use. See DtlsConnection.get_protocol_version.

rehandshake_mode

rehandshake_mode: TlsRehandshakeMode | int  # read/write

:::warning Deprecated since 2.60 This API is deprecated. :::

The rehandshaking mode. See DtlsConnection.set_rehandshake_mode.

require_close_notify

require_close_notify: bool  # read/write

Whether or not proper TLS close notification is required. See DtlsConnection.set_require_close_notify.

Signals

accept-certificate

def on_accept_certificate(self, peer_cert: TlsCertificate, errors: TlsCertificateFlags) -> bool: ...

Emitted during the TLS handshake after the peer certificate has been received. You can examine peer_cert's certification path by calling TlsCertificate.get_issuer on it.

For a client-side connection, peer_cert is the server's certificate, and the signal will only be emitted if the certificate was not acceptable according to conn's DtlsClientConnection:validation_flags. If you would like the certificate to be accepted despite errors, return True from the signal handler. Otherwise, if no handler accepts the certificate, the handshake will fail with TlsError.BAD_CERTIFICATE.

GLib guarantees that if certificate verification fails, this signal will be emitted with at least one error will be set in errors, 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 ignore 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.

For a server-side connection, peer_cert is the certificate presented by the client, if this was requested via the server's DtlsServerConnection:authentication_mode. On the server side, the signal is always emitted when the client presents a certificate, and the certificate will only be accepted if a handler returns True.

Note that if this signal is emitted as part of asynchronous I/O in the main thread, then you should not attempt to interact with the user before returning from the signal handler. If you want to let the user decide whether or not to accept the certificate, you would have to return False from the signal handler on the first attempt, and then after the connection attempt returns a TlsError.BAD_CERTIFICATE, you can interact with the user, and if the user decides to accept the certificate, remember that fact, create a new connection, and return True from the signal handler the next time.

If you are doing I/O in another thread, you do not need to worry about this, and can simply block in the signal handler until the UI thread returns an answer.