bus_dispatch_sha1_test on Windows

Peter Kümmel syntheticpp at gmx.net
Sun Nov 26 13:18:35 PST 2006


Havoc Pennington wrote:
> Peter Kümmel wrote:
>>
>> signal sender=(null sender) -> dest=(null destination)
>> path=/org/freedesktop/DBus/Local;
>> interface=org.freedesktop.DBus.Local;
>> member=Disconnected
> 
> That should be a helpful lead - you just need to figure out why the
> connection gets dropped.

Seems it is a authentication problem.
I get this verbose output:

...
Running SHA1 connection test
...
1524: client: Sent 26 bytes of: AUTH EXTERNAL 3439323731
...
1524: server: got command "AUTH EXTERNAL 3439323731"
1524: server: Unsupported mechanism EXTERNAL

the mechanism is unsupported, because it wants a DBUS_COOKIE_SHA1.

      auth->mech = find_mech (&mech, auth->allowed_mechs); <---- returns NULL
      if (auth->mech != NULL)
        {
          _dbus_verbose ("%s: Trying mechanism %s\n",
                         DBUS_AUTH_NAME (auth),
                         auth->mech->mechanism);

          if (!process_data (auth, &hex_response,
                             auth->mech->server_data_func))
            goto failed;
        }
	else
        {
          /* Unsupported mechanism */
          _dbus_verbose ("%s: Unsupported mechanism %s\n",
                         DBUS_AUTH_NAME (auth),
                         _dbus_string_get_const_data (&mech));

          if (!send_rejected (auth))
            goto failed;
        }

then the connection is closed:

1592: Sending disconnect message from notify_disconnected_and_dispatch_complete_unlocked


But I've no idea why there is a AUTH EXTERNAL instead of a SHA1 mechanism.


Peter


More information about the dbus mailing list