bus_dispatch_sha1_test on Windows

Peter Kümmel syntheticpp at gmx.net
Tue Nov 28 06:40:06 PST 2006


Havoc Pennington wrote:
> 
> 
> Peter Kümmel wrote:
>> But I've no idea why there is a AUTH EXTERNAL instead of a SHA1
>> mechanism.
>>
> 
> I think this is normal, it gets unsupported for EXTERNAL so it should
> then try SHA1 instead.
> 
> Have you implemented the SHA1 mechanism on Windows? Should it even work?
> 
> Maybe you will have to step through in a debugger or add more verbose
> output to understand why the disconnection occurs.
> 
> Havoc
> 

UPDATE: sometimes the SHA1 mechanism fails.


Running SHA1 connection test

client: going from state NeedSendAuth to state WaitingForData
client: Sent 26 bytes of: AUTH EXTERNAL 3439313939

server: got command "AUTH EXTERNAL 3439313939"
server: Unsupported mechanism EXTERNAL
server: going from state WaitingForAuth to state WaitingForAuth
server: Sent 36 bytes of: REJECTED EXTERNAL DBUS_COOKIE_SHA1

client: got command "REJECTED EXTERNAL DBUS_COOKIE_SHA1"
client: Already tried mechanism EXTERNAL; not adding to list we will try
client: Adding mechanism DBUS_COOKIE_SHA1 to list we will try
client: Shutting down mechanism EXTERNAL
client: going from state WaitingForData to state WaitingForData
client: Trying mechanism DBUS_COOKIE_SHA1
client: Sent 54 bytes of: AUTH DBUS_COOKIE_SHA1 43434f4d50555445525c6375736572

server: got command "AUTH DBUS_COOKIE_SHA1 43434f4d50555445525c6375736572"
server: Trying mechanism DBUS_COOKIE_SHA1
server: data: 'CCOMPUTER\cuser'
server: going from state WaitingForAuth to state WaitingForData
server: Sent 139 bytes of: DATA 6f72675f667265656465736b746f705f67656e6572616c20333132383138363838203030336361353132343435623431666235316565326464613038303239663762

client: got command "DATA 6f72675f667265656465736b746f705f67656e6572616c20333132383138363838203030336361353132343435623431666235316565326464613038303239663762"
client: data: 'org_freedesktop_general 312818688 003ca512445b41fb51ee2dda08029f7b'
client: Sent 44 bytes of: ERROR "Don't have the requested cookie ID"

server: got command "ERROR "Don't have the requested cookie ID""
server: Shutting down mechanism DBUS_COOKIE_SHA1
server: going from state WaitingForData to state WaitingForAuth
server: Sent 36 bytes of: REJECTED EXTERNAL DBUS_COOKIE_SHA1

client: got command "REJECTED EXTERNAL DBUS_COOKIE_SHA1"
client: Disconnecting because we are out of mechanisms to try using
client: going from state WaitingForData to state NeedDisconnect
spin_connection_until_authenticated failed,


Maybe because of a locked file? Have to figure out why.

Peter


More information about the dbus mailing list