winDBus authentication stage

[Ralf Habacker]

Havoc Pennington schrieb:
>
>
> Alp Toker wrote:
>> I have some managed D-Bus (http://www.ndesk.org/DBusSharp) users who
>> are connecting to the winDBus daemon on Win32.
>>
>> They are using the "tcp" transport and made a couple of observations:
>>
>> 1) winDBus doesn't accept a null byte at the very start of the
>> stream. My users had to modify the managed tcp transport not to send
>> the null byte. I had the impression that this byte would always be
>> sent and accepted to provide consistency with other transports where
>> it is used to provide peer credentials.
This wasn't implemented. I'm going to fix this in the next time.
>>
>> 2) The EXTERNAL authentication mechanism used on the winDBus tcp
>> transport seems to require a global atom representing the user SID as
>> a string (where the unix uid would usually be as a string). What is
>> the the reasoning behind this?
There was an ongoing discussion that windows dbus should does have a
different authentification scheme because user id's are not available on
windows. Havoc can say more to this item.

>>
>> I'd like to provide interoperability between managed D-Bus and
>> winDBus in my next release, so please advise as to whether (1) is a
>> bug or a feature and whether I should integrate code to provide the
>> functionality required by (2).
>>
>
> windbus is still totally busted afaik. 
Do you ever tried windbus ? It may be not complete and there are some
outstanding patches to be full integrated in dbus cvs (although windbus
could be build now completly from dbus-cvs).
It is running for about a half year with kde on windows without any
problems.

> Both 1) and 2) are bugs.
1) yes
2) design isn't finished, what to send over the wire for windows.
> I would not bother trying to support dbus on win32 until we get it
> integrated into the dbus mainline.
Why not - the more developers are using the current code, the more input
comes  and integration into dbus-cvs would be nearer in the future.

Ralf