Interface DtlsConnection
- All Superinterfaces:
DatagramBased,Proxy
- All Known Subinterfaces:
DtlsClientConnection,DtlsServerConnection
- All Known Implementing Classes:
DtlsClientConnection.DtlsClientConnection$Impl,DtlsConnection.DtlsConnection$Impl,DtlsServerConnection.DtlsServerConnection$Impl
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 (Gio.DtlsConnection:base-socket).
To close a DTLS connection, use close(org.gnome.gio.Cancellable).
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.
- Since:
- 2.48
-
Nested Class Summary
Nested ClassesModifier and TypeInterfaceDescriptionstatic interfaceFunctional interface declaration of theAcceptCertificateCallbackcallback.static interfaceDtlsConnection.Builder<B extends Builder<B>>static classThe DtlsConnection$Impl type represents a native instance of the DtlsConnection interface.static classVirtual method table for aGDtlsConnectionimplementation.Nested classes/interfaces inherited from interface org.gnome.gio.DatagramBased
DatagramBased.DatagramBased$Impl, DatagramBased.DatagramBasedInterface -
Method Summary
Modifier and TypeMethodDescriptiondefault booleanclose(@Nullable Cancellable cancellable) Close the DTLS connection.default voidcloseAsync(int ioPriority, @Nullable Cancellable cancellable, @Nullable AsyncReadyCallback callback) Asynchronously close the DTLS connection.default booleancloseFinish(AsyncResult result) Finish an asynchronous TLS close operation.default booleanemitAcceptCertificate(TlsCertificate peerCert, Set<TlsCertificateFlags> errors) Used byGDtlsConnectionimplementations to emit theGDtlsConnection::accept-certificate signal.default booleanemitAcceptCertificate(TlsCertificate peerCert, TlsCertificateFlags... errors) Used byGDtlsConnectionimplementations to emit theGDtlsConnection::accept-certificate signal.default @Nullable TlsCertificateGetsconn'scertificate, as set by g_dtls_connection_set_certificate().default booleangetChannelBindingData(TlsChannelBindingType type, @Nullable Out<byte[]> data) Query the TLS backend for TLS channel binding data oftypeforconn.default @Nullable StringReturns the name of the current DTLS ciphersuite, ornullif the connection has not handshaked or has been closed.default @Nullable TlsDatabaseGets the certificate database that this DtlsConnection uses to verify peer certificates.default @Nullable TlsInteractionGet the object that will be used to interact with the user.default @Nullable StringGets the name of the application-layer protocol negotiated during the handshake.default @Nullable TlsCertificateGetsconn'speer's certificate after the handshake has completed or failed.default Set<TlsCertificateFlags> Gets the errors associated with validatingconn'speer's certificate, after the handshake has completed or failed.default TlsProtocolVersionReturns the current DTLS protocol version, which may beTlsProtocolVersion.UNKNOWNif the connection has not handshaked, or has been closed, or if the TLS backend has implemented a protocol version that is not a recognizedGTlsProtocolVersion.default TlsRehandshakeModeDeprecated.Changing the rehandshake mode is no longer required for compatibility.default booleanTests whether or not this DtlsConnection expects a proper TLS close notification when the connection is closed.static @Nullable TypegetType()Get the GType of the DtlsConnection classdefault booleanhandshake(@Nullable Cancellable cancellable) Attempts a TLS handshake onconn.default voidhandshakeAsync(int ioPriority, @Nullable Cancellable cancellable, @Nullable AsyncReadyCallback callback) Asynchronously performs a TLS handshake onconn.See g_dtls_connection_handshake() for more information.default booleanhandshakeFinish(AsyncResult result) Finish an asynchronous TLS handshake operation.Emitted during the TLS handshake after the peer certificate has been received.default voidsetAdvertisedProtocols(@Nullable String @Nullable [] protocols) Sets the list of application-layer protocols to advertise that the caller is willing to speak on this connection.default voidsetCertificate(TlsCertificate certificate) This sets the certificate that this DtlsConnection will present to its peer during the TLS handshake.default voidsetDatabase(@Nullable TlsDatabase database) Sets the certificate database that is used to verify peer certificates.default voidsetInteraction(@Nullable TlsInteraction interaction) Set the object that will be used to interact with the user.default voidDeprecated.Changing the rehandshake mode is no longer required for compatibility.default voidsetRequireCloseNotify(boolean requireCloseNotify) Sets whether or not this DtlsConnection expects a proper TLS close notification before the connection is closed.default booleanshutdown(boolean shutdownRead, boolean shutdownWrite, @Nullable Cancellable cancellable) Shut down part or all of a DTLS connection.default voidshutdownAsync(boolean shutdownRead, boolean shutdownWrite, int ioPriority, @Nullable Cancellable cancellable, @Nullable AsyncReadyCallback callback) Asynchronously shut down part or all of the DTLS connection.default booleanshutdownFinish(AsyncResult result) Finish an asynchronous TLS shutdown operation.Methods inherited from interface org.gnome.gio.DatagramBased
conditionCheck, conditionCheck, conditionWait, conditionWait, createSource, createSource, receiveMessages, sendMessages
-
Method Details
-
getType
-
close
Close the DTLS connection. This is equivalent to calling g_dtls_connection_shutdown() to shut down both sides of the connection.Closing a
GDtlsConnectionwaits for all buffered but untransmitted data to be sent before it completes. It then sends aclose_notifyDTLS alert to the peer and may wait for aclose_notifyto be received from the peer. It does not close the underlyingGDtlsConnection:base-socket; that must be closed separately.Once this DtlsConnection is closed, all other operations will return
IOErrorEnum.CLOSED. Closing aGDtlsConnectionmultiple times will not return an error.GDtlsConnectionswill 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
cancellableis cancelled, theGDtlsConnectionmay be left partially-closed and any pending untransmitted data may be lost. Call g_dtls_connection_close() again to complete closing theGDtlsConnection.- Parameters:
cancellable- aGCancellable, ornull- Returns:
trueon success,falseotherwise- Throws:
GErrorException- seeGError- Since:
- 2.48
-
closeAsync
default void closeAsync(int ioPriority, @Nullable Cancellable cancellable, @Nullable AsyncReadyCallback callback) Asynchronously close the DTLS connection. See g_dtls_connection_close() for more information.- Parameters:
ioPriority- the I/O priority of the requestcancellable- aGCancellable, ornullcallback- callback to call when the close operation is complete- Since:
- 2.48
-
closeFinish
Finish an asynchronous TLS close operation. See g_dtls_connection_close() for more information.- Parameters:
result- aGAsyncResult- Returns:
trueon success,falseon failure, in which caseerrorwill be set- Throws:
GErrorException- seeGError- Since:
- 2.48
-
emitAcceptCertificate
Used byGDtlsConnectionimplementations to emit theGDtlsConnection::accept-certificate signal.- Parameters:
peerCert- the peer'sGTlsCertificateerrors- the problems withpeerCert- Returns:
trueif one of the signal handlers has returnedtrueto acceptpeerCert- Since:
- 2.48
-
emitAcceptCertificate
Used byGDtlsConnectionimplementations to emit theGDtlsConnection::accept-certificate signal.- Parameters:
peerCert- the peer'sGTlsCertificateerrors- the problems withpeerCert- Returns:
trueif one of the signal handlers has returnedtrueto acceptpeerCert- Since:
- 2.48
-
getCertificate
Getsconn'scertificate, as set by g_dtls_connection_set_certificate().- Returns:
conn'scertificate, ornull- Since:
- 2.48
-
getChannelBindingData
default boolean getChannelBindingData(TlsChannelBindingType type, @Nullable Out<byte[]> data) throws GErrorException Query the TLS backend for TLS channel binding data oftypeforconn.This call retrieves TLS channel binding data as specified in RFC 5056, RFC 5929, and related RFCs. The binding data is returned in
data.Thedatais resized by the callee usingGByteArraybuffer management and will be freed when thedatais destroyed by g_byte_array_unref(). Ifdataisnull, it will only check whether TLS backend is able to fetch the data (e.g. whethertypeis supported by the TLS backend). It does not guarantee that the data will be available though. That could happen if TLS connection does not supporttypeor the binding data is not available yet due to additional negotiation or input required.- Parameters:
type-GTlsChannelBindingTypetype of data to fetchdata-GByteArrayis filled with the binding data, ornull- Returns:
trueon success,falseotherwise- Throws:
GErrorException- seeGError- Since:
- 2.66
-
getCiphersuiteName
Returns the name of the current DTLS ciphersuite, ornullif 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.- Returns:
- The name of the current DTLS ciphersuite, or
null - Since:
- 2.70
-
getDatabase
Gets the certificate database that this DtlsConnection uses to verify peer certificates. See g_dtls_connection_set_database().- Returns:
- the certificate database that this DtlsConnection uses or
null - Since:
- 2.48
-
getInteraction
Get the object that will be used to interact with the user. It will be used for things like prompting the user for passwords. Ifnullis returned, then no user interaction will occur for this connection.- Returns:
- The interaction object.
- Since:
- 2.48
-
getNegotiatedProtocol
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'sprotocols, or the TLS backend does not support ALPN, then this will benull. See g_dtls_connection_set_advertised_protocols().- Returns:
- the negotiated protocol, or
null - Since:
- 2.60
-
getPeerCertificate
Getsconn'speer's certificate after the handshake has completed or failed. (It is not set during the emission ofGDtlsConnection::accept-certificate.)- Returns:
conn'speer's certificate, ornull- Since:
- 2.48
-
getPeerCertificateErrors
Gets the errors associated with validatingconn'speer's certificate, after the handshake has completed or failed. (It is not set during the emission ofGDtlsConnection::accept-certificate.)- Returns:
conn'speer's certificate errors- Since:
- 2.48
-
getProtocolVersion
Returns the current DTLS protocol version, which may beTlsProtocolVersion.UNKNOWNif the connection has not handshaked, or has been closed, or if the TLS backend has implemented a protocol version that is not a recognizedGTlsProtocolVersion.- Returns:
- The current DTLS protocol version
- Since:
- 2.70
-
getRehandshakeMode
Deprecated.Changing the rehandshake mode is no longer required for compatibility. Also, rehandshaking has been removed from the TLS protocol in TLS 1.3.Gets this DtlsConnection rehandshaking mode. See g_dtls_connection_set_rehandshake_mode() for details.- Returns:
TlsRehandshakeMode.SAFELY- Since:
- 2.48
-
getRequireCloseNotify
default boolean getRequireCloseNotify()Tests whether or not this DtlsConnection expects a proper TLS close notification when the connection is closed. See g_dtls_connection_set_require_close_notify() for details.- Returns:
trueif this DtlsConnection requires a proper TLS close notification.- Since:
- 2.48
-
handshake
Attempts a TLS handshake onconn.On the client side, it is never necessary to call this method; although the connection needs to perform a handshake after connecting,
GDtlsConnectionwill handle this for you automatically when you try to send or receive data on the connection. You can call g_dtls_connection_handshake() manually if you want to know whether the initial handshake succeeded or failed (as opposed to just immediately trying to use this DtlsConnection 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 g_dtls_connection_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.
GDtlsConnection::accept_certificate may be emitted during the handshake.- Parameters:
cancellable- aGCancellable, ornull- Returns:
- success or failure
- Throws:
GErrorException- seeGError- Since:
- 2.48
-
handshakeAsync
default void handshakeAsync(int ioPriority, @Nullable Cancellable cancellable, @Nullable AsyncReadyCallback callback) Asynchronously performs a TLS handshake onconn.See g_dtls_connection_handshake() for more information.- Parameters:
ioPriority- the I/O priority of the requestcancellable- aGCancellable, ornullcallback- callback to call when the handshake is complete- Since:
- 2.48
-
handshakeFinish
Finish an asynchronous TLS handshake operation. See g_dtls_connection_handshake() for more information.- Parameters:
result- aGAsyncResult.- Returns:
trueon success,falseon failure, in which caseerrorwill be set.- Throws:
GErrorException- seeGError- Since:
- 2.48
-
setAdvertisedProtocols
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 g_dtls_connection_get_negotiated_protocol() to find the negotiated protocol after the handshake. Specifyingnullfor the the value ofprotocolswill disable ALPN negotiation.See IANA TLS ALPN Protocol IDs for a list of registered protocol IDs.
- Parameters:
protocols- anull-terminated array of ALPN protocol names (eg, "http/1.1", "h2"), ornull- Since:
- 2.60
-
setCertificate
This sets the certificate that this DtlsConnection will present to its peer during the TLS handshake. For aGDtlsServerConnection, it is mandatory to set this, and that will normally be done at construct time.For a
GDtlsClientConnection, this is optional. If a handshake fails withTlsError.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 g_dtls_client_connection_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 g_dtls_client_connection_get_accepted_cas() will return non-
null.)- Parameters:
certificate- the certificate to use for this DtlsConnection- Since:
- 2.48
-
setDatabase
Sets the certificate database that is used to verify peer certificates. This is set to the default database by default. See g_tls_backend_get_default_database(). If set tonull, then peer certificate validation will always set theTlsCertificateFlags.UNKNOWN_CAerror (meaningGDtlsConnection::accept-certificate will always be emitted on client-side connections, unless that bit is not set inGDtlsClientConnection:validation-flags).There are nonintuitive security implications when using a non-default database. See
GDtlsConnection:database for details.- Parameters:
database- aGTlsDatabase- Since:
- 2.48
-
setInteraction
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
interactionargument will normally be a derived subclass ofGTlsInteraction.nullcan also be provided if no user interaction should occur for this connection.- Parameters:
interaction- an interaction object, ornull- Since:
- 2.48
-
setRehandshakeMode
Deprecated.Changing the rehandshake mode is no longer required for compatibility. Also, rehandshaking has been removed from the TLS protocol in TLS 1.3.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- Since:
- 2.48
-
setRequireCloseNotify
default void setRequireCloseNotify(boolean requireCloseNotify) Sets whether or not this DtlsConnection expects a proper TLS close notification before the connection is closed. If this istrue(the default), then this DtlsConnection will expect to receive a TLS close notification from its peer before the connection is closed, and will return aTlsError.EOFerror 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 g_dtls_connection_set_require_close_notify() to tell this DtlsConnection to allow an "unannounced" connection close, in which case the close will show up as a 0-length read, as in a non-TLS
GDatagramBased, 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 g_dtls_connection_close_async() on this DtlsConnection 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'sGDtlsConnection:base-socket rather than closing this DtlsConnection itself.- Parameters:
requireCloseNotify- whether or not to require close notification- Since:
- 2.48
-
shutdown
default boolean shutdown(boolean shutdownRead, boolean shutdownWrite, @Nullable Cancellable cancellable) throws GErrorException Shut down part or all of a DTLS connection.If
shutdownReadistruethen the receiving side of the connection is shut down, and further reading is disallowed. Subsequent calls to g_datagram_based_receive_messages() will returnIOErrorEnum.CLOSED.If
shutdownWriteistruethen the sending side of the connection is shut down, and further writing is disallowed. Subsequent calls to g_datagram_based_send_messages() will returnIOErrorEnum.CLOSED.It is allowed for both
shutdownReadandshutdownWriteto be TRUE — this is equivalent to calling g_dtls_connection_close().If
cancellableis cancelled, theGDtlsConnectionmay be left partially-closed and any pending untransmitted data may be lost. Call g_dtls_connection_shutdown() again to complete closing theGDtlsConnection.- Parameters:
shutdownRead-trueto stop reception of incoming datagramsshutdownWrite-trueto stop sending outgoing datagramscancellable- aGCancellable, ornull- Returns:
trueon success,falseotherwise- Throws:
GErrorException- seeGError- Since:
- 2.48
-
shutdownAsync
default void shutdownAsync(boolean shutdownRead, boolean shutdownWrite, int ioPriority, @Nullable Cancellable cancellable, @Nullable AsyncReadyCallback callback) Asynchronously shut down part or all of the DTLS connection. See g_dtls_connection_shutdown() for more information.- Parameters:
shutdownRead-trueto stop reception of incoming datagramsshutdownWrite-trueto stop sending outgoing datagramsioPriority- the I/O priority of the requestcancellable- aGCancellable, ornullcallback- callback to call when the shutdown operation is complete- Since:
- 2.48
-
shutdownFinish
Finish an asynchronous TLS shutdown operation. See g_dtls_connection_shutdown() for more information.- Parameters:
result- aGAsyncResult- Returns:
trueon success,falseon failure, in which caseerrorwill be set- Throws:
GErrorException- seeGError- Since:
- 2.48
-
onAcceptCertificate
default SignalConnection<DtlsConnection.AcceptCertificateCallback> onAcceptCertificate(DtlsConnection.AcceptCertificateCallback handler) Emitted during the TLS handshake after the peer certificate has been received. You can examinepeerCert'scertification path by calling g_tls_certificate_get_issuer() on it.For a client-side connection,
peerCertis the server's certificate, and the signal will only be emitted if the certificate was not acceptable according toconn'sGDtlsClientConnection:validation_flags. If you would like the certificate to be accepted despiteerrors,returntruefrom the signal handler. Otherwise, if no handler accepts the certificate, the handshake will fail withTlsError.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 ignoreTlsCertificateFlags.EXPIREDif 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,
peerCertis the certificate presented by the client, if this was requested via the server'sGDtlsServerConnection: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 returnstrue.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
falsefrom the signal handler on the first attempt, and then after the connection attempt returns aTlsError.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 returntruefrom 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.
- Parameters:
handler- the signal handler- Returns:
- a signal handler ID to keep track of the signal connection
- Since:
- 2.48
- See Also:
-