:right-sidebar: True

TlsChannelBindingError
===================================================================

.. currentmodule:: gi.repository.Gio


.. versionadded:: 2.66




.. class:: TlsChannelBindingError
   :no-contents-entry:






An error code used with ``%G_TLS_CHANNEL_BINDING_ERROR`` in a :obj:`~gi.repository.GLib.Error` to
indicate a TLS channel binding retrieval error.





Methods
-------

.. rst-class:: interim-class

.. class:: TlsChannelBindingError
   :no-index:


   .. method:: quark() -> int

      Gets the TLS channel binding error quark.



      .. versionadded:: 2.66


















Fields
------

.. rst-class:: interim-class

.. class:: TlsChannelBindingError
   :no-index:
   

   .. attribute:: GENERAL_ERROR

      Any other backend error
      preventing binding data retrieval.







   .. attribute:: INVALID_STATE

      The handshake is not yet
      complete on the connection which is a strong requirement for any existing
      binding type.







   .. attribute:: NOT_AVAILABLE

      Handshake is complete but
      binding data is not available. That normally indicates the TLS
      implementation failed to provide the binding data. For example, some
      implementations do not provide a peer certificate for resumed connections.







   .. attribute:: NOT_IMPLEMENTED

      Either entire binding
      retrieval facility or specific binding type is not implemented in the
      TLS backend.







   .. attribute:: NOT_SUPPORTED

      Binding type is not supported
      on the current connection. This error could be triggered when requesting
      ``tls-server-end-point`` binding data for a certificate which has no hash
      function or uses multiple hash functions.