:right-sidebar: True

DBusConnectionFlags
===================================================================

.. currentmodule:: gi.repository.Gio


.. versionadded:: 2.26




.. class:: DBusConnectionFlags
   :no-contents-entry:






Flags used when creating a new :obj:`~gi.repository.Gio.DBusConnection`.













Fields
------

.. rst-class:: interim-class

.. class:: DBusConnectionFlags
   :no-index:
   

   .. attribute:: AUTHENTICATION_ALLOW_ANONYMOUS

      When
      authenticating as a server, allow the anonymous authentication
      method.







   .. attribute:: AUTHENTICATION_CLIENT

      Perform authentication against server.







   .. attribute:: AUTHENTICATION_REQUIRE_SAME_USER

      When authenticating
      as a server, require the UID of the peer to be the same as the UID of the server. (Since: 2.68)







   .. attribute:: AUTHENTICATION_SERVER

      Perform authentication against client.







   .. attribute:: CROSS_NAMESPACE

      When authenticating, try to use
      protocols that work across a Linux user namespace boundary, even if this
      reduces interoperability with older D-Bus implementations. This currently
      affects client-side ``EXTERNAL`` authentication, for which this flag makes
      connections to a server in another user namespace succeed, but causes
      a deadlock when connecting to a GDBus server older than 2.73.3. Since: 2.74







   .. attribute:: DELAY_MESSAGE_PROCESSING

      If set, processing of D-Bus messages is
      delayed until :func:`~gi.repository.Gio.DBusConnection.start_message_processing` is called.







   .. attribute:: MESSAGE_BUS_CONNECTION

      Pass this flag if connecting to a peer that is a
      message bus. This means that the Hello() method will be invoked as part of the connection setup.







   .. attribute:: NONE

      No flags set.