dbus-java and windbus

[Christian Ehrlicher]

> Von: "Jacques-Olivier Goussard"
> So I set
> <auth>DBUS_COOKIE_SHA1</auth>
> in the daemon configuration.
> I use
> DBUS_TEST_HOMEDIR=C:/tmp
> in the daemon environment and
> -Duser.home=C:/tmp
> on the client java command line - both should read/write the cookies from
> the
> proper place right ? The doc is really thin on those issues.
> I get :
> 15684: server: got command "AUTH DBUS_COOKIE_SHA1 6a6f67"
> 15684: server: Trying mechanism DBUS_COOKIE_SHA1
> 15684: server: data: 'jog'
> 15684: Using fake homedir for testing: C:/tmp
> ...
> 15684: server: data: '821f3865ae9ebb4af7e7e9ffafa31c9f2309117b
> 5df4c83adaa60c550
> f38edb1d121cadba04e6dbb'
> 15684: server: going from state WaitingForData to state WaitingForBegin
> 15684: server: authenticated client using DBUS_COOKIE_SHA1
> 15684: exchange_credentials: do_reading = 1, do_writing = 0
> ...
> 15684: server: got command "BEGIN"
> 15684: server: going from state WaitingForBegin to state Authenticated
> 15684: _dbus_getsid() returns 1
> 15684: Client authorized as SID
> 'S-1-5-21-52702793-1996691837-315576832-2805' bu
> t our SID is 'S-1-5-21-52702793-1996691837-315576832-2805', disconnecting
> 15684: _dbus_transport_disconnect start
> ...
> and it fails.
> This is with the DBusVIewer client from dbus-java-2.4.
> Log attached.
Just out of curiosity  - what windbus do you use? Where do you have it from?


Christian

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger