Gio.DtlsClientConnection¶
- Implementations:
None
Methods¶
class |
|
|
|
|
Virtual Methods¶
None
Properties¶
Name |
Type |
Flags |
Short Description |
---|---|---|---|
r |
|||
r/w/c |
|||
r/w/c |
|
Signals¶
None
Fields¶
None
Class Details¶
- class Gio.DtlsClientConnection¶
- Bases:
- Structure:
GDtlsClientConnection
is the client-side subclass of [iface`Gio`.DtlsConnection], representing a client-side DTLS connection.New in version 2.48.
- classmethod new(base_socket, server_identity)[source]¶
- Parameters:
base_socket (
Gio.DatagramBased
) – theGio.DatagramBased
to wrapserver_identity (
Gio.SocketConnectable
orNone
) – the expected identity of the server
- Raises:
- Returns:
the new
Gio.DtlsClientConnection
, orNone
on error- Return type:
Creates a new
Gio.DtlsClientConnection
wrapping base_socket which is assumed to communicate with the server identified by server_identity.New in version 2.48.
- get_accepted_cas()[source]¶
- Returns:
the list of CA DNs. You should unref each element with
GLib.ByteArray.unref
() and then the free the list with g_list_free().- Return type:
[
bytes
]
Gets the list of distinguished names of the Certificate Authorities that the server will accept certificates from. This will be set during the TLS handshake if the server requests a certificate. Otherwise, it will be
None
.Each item in the list is a
GLib.ByteArray
which contains the complete subject DN of the certificate authority.New in version 2.48.
- get_server_identity()[source]¶
- Returns:
a
Gio.SocketConnectable
describing the expected server identity, orNone
if the expected identity is not known.- Return type:
Gets self's expected server identity
New in version 2.48.
- get_validation_flags()[source]¶
- Returns:
the validation flags
- Return type:
Gets self's validation flags
This function does not work as originally designed and is impossible to use correctly. See
Gio.DtlsClientConnection
:validation-flags
for more information.New in version 2.48.
Deprecated since version 2.74: Do not attempt to ignore validation errors.
- set_server_identity(identity)[source]¶
- Parameters:
identity (
Gio.SocketConnectable
) – aGio.SocketConnectable
describing the expected server identity
Sets self's expected server identity, which is used both to tell servers on virtual hosts which certificate to present, and also to let self know what name to look for in the certificate when performing
Gio.TlsCertificateFlags.BAD_IDENTITY
validation, if enabled.New in version 2.48.
- set_validation_flags(flags)[source]¶
- Parameters:
flags (
Gio.TlsCertificateFlags
) – theGio.TlsCertificateFlags
to use
Sets self's validation flags, to override the default set of checks performed when validating a server certificate. By default,
Gio.TlsCertificateFlags.VALIDATE_ALL
is used.This function does not work as originally designed and is impossible to use correctly. See
Gio.DtlsClientConnection
:validation-flags
for more information.New in version 2.48.
Deprecated since version 2.74: Do not attempt to ignore validation errors.
Property Details¶
- Gio.DtlsClientConnection.props.accepted_cas¶
-
A list of the distinguished names of the Certificate Authorities that the server will accept client certificates signed by. If the server requests a client certificate during the handshake, then this property will be set after the handshake completes.
Each item in the list is a
GLib.ByteArray
which contains the complete subject DN of the certificate authority.New in version 2.48.
- Gio.DtlsClientConnection.props.server_identity¶
- Name:
server-identity
- Type:
- Default Value:
- Flags:
A
Gio.SocketConnectable
describing the identity of the server that is expected on the other end of the connection.If the
Gio.TlsCertificateFlags.BAD_IDENTITY
flag is set inGio.DtlsClientConnection
:validation-flags
, this object will be used to determine the expected identify of the remote end of the connection; ifGio.DtlsClientConnection
:server-identity
is not set, or does not match the identity presented by the server, then theGio.TlsCertificateFlags.BAD_IDENTITY
validation will fail.In addition to its use in verifying the server certificate, this is also used to give a hint to the server about what certificate we expect, which is useful for servers that serve virtual hosts.
New in version 2.48.
- Gio.DtlsClientConnection.props.validation_flags¶
- Name:
validation-flags
- Type:
- Default Value:
Gio.TlsCertificateFlags.UNKNOWN_CA
|Gio.TlsCertificateFlags.BAD_IDENTITY
|Gio.TlsCertificateFlags.NOT_ACTIVATED
|Gio.TlsCertificateFlags.EXPIRED
|Gio.TlsCertificateFlags.REVOKED
|Gio.TlsCertificateFlags.INSECURE
|Gio.TlsCertificateFlags.GENERIC_ERROR
|Gio.TlsCertificateFlags.VALIDATE_ALL
- Flags:
What steps to perform when validating a certificate received from a server. Server certificates that fail to validate in any of the ways indicated here will be rejected unless the application overrides the default via
Gio.DtlsConnection
::accept-certificate
.GLib guarantees that if certificate verification fails, at least one flag will be set, but it does not guarantee that all possible flags 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. Therefore, there is no safe way to use this property. This is not a horrible problem, though, because you should not be attempting to ignore validation errors anyway. If you really must ignore TLS certificate errors, connect toGio.DtlsConnection
::accept-certificate
.New in version 2.48.
Deprecated since version 2.74: Do not attempt to ignore validation errors.