getting remote sys to talk to local dbus

[L A Walsh]

STarted out with:
> echo $DBUS_SESSION_BUS_ADDRESS
tcp:host=Athenae.hs.tlinx.org,port=1234,guid=3ff81b6870df706b11bd91d552f18138
> ssh ishtar
> echo $DBUS_SESSION_BUS_ADDRESS      
unix:abstract=/tmp/dbus-V9CYFVcCNc,guid=e2ed19cfafb1a9f528c0bf2652b96ab4
qdbus
Ishtar:law> Could not connect to D-Bus server: 
org.freedesktop.DBus.Error.NoServer: Failed to connect to socket 
/tmp/dbus-V9CYFVcCNc: Connection refused

--- Figured out how to forwar DBUS vars through ssh, so now:


> echo $DBUS_SESSION_BUS_ADDRESS
tcp:host=Athenae.hs.tlinx.org,port=1234,guid=3ff81b6870df706b11bd91d552f18138
/etc/dbus-1> ssh ishtar
DBUS_SESSION_BUS_ADDRESS=tcp:host=Athenae.hs.tlinx.org,port=1234,guid=3ff81b6870df706b11bd91d552f18138
> echo $DBUS_SESSION_BUS_ADDRESS
tcp:host=Athenae.hs.tlinx.org,port=1234,guid=3ff81b6870df706b11bd91d552f18138

And seems to be getting further:  (no immediate denial, it tries and times out:
Ishtar:law> qdbus
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoReply: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.

As near as I can tell my session bus on my local system doesn't have any blocking
policies:
   <listen>tcp:host=Athenae.hs.tlinx.org,port=1234</listen>

   <standard_session_servicedirs />

   <policy context="default">
     <!-- Allow everything to be sent -->
     <allow send_destination="*" eavesdrop="true"/>
     <!-- Allow everything to be received -->
     <allow eavesdrop="true"/>
     <!-- Allow anyone to own anything -->
     <allow own="*"/>
   </policy>

----

So why isn't my local dbus responding?

It seems to be alive:
/etc/dbus-1> dbus-monitor.exe
signal sender=org.freedesktop.DBus -> dest=:1.1 serial=2 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
    string ":1.1"
method call sender=:1.1 -> dest=org.freedesktop.DBus serial=3 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
    string "eavesdrop=true,type='method_call'"
method call sender=:1.1 -> dest=org.freedesktop.DBus serial=4 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
    string "eavesdrop=true,type='method_return'"
method call sender=:1.1 -> dest=org.freedesktop.DBus serial=5 
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
    string "eavesdrop=true,type='error'"

----

Looking at the the conversation, I see (ish=remote, loc=local)
ish: auth external #####
loc:   REJECTED EXTERNAL DBUS_COOKIE_SHA1 ANONYMOUS\x0d\x0
Ish:   AUTH DBUS_COOKIE_SHA1 12345678\r\n
loc:    DATA (big long string of hex data (~128 byte cookie?)
Ish:    Error "Don't have the requested cookie ID"
local   rejected external dbus_cookie_sha1 anonymouse
Ish:     auth anonymous?  #####
local    OK ##########
Ish:    Begin:
local:   <hangs up / closes connection>

How rude!?

Ish tries a few more times then gives up.

why would local say ok, then as soon as Ish tries to begin,
"click"...bzzzzz (hangup)...

Ishtar is feeling a bit distressed now, especially, since it just
let local "ssh" into it -- and what does it get for that?

rudeness! ;-)...

ok... anyone have an idea what's going on and howI might get these
guys talking a bit mroe...


One of the things I'd really like is when I'm running a prog on Ishtar
and it calls for a weblink, I'd rather my local browser come up rather
than one on ishtar over 'X11'....   it's a bit slow....


But getting some better integration in other things would be great!


FWIW,
local is a Win7-running cygwin64 -- so it has a dbus or two (sys+session),

and remote is a linux/open-snuzey(suse) system...

right now am limited to X displays but no desktop integration
(not to mention remote doesn't really run a desktop as it is
a server with minimal graphics support.

Ideas?

Thanks much!







????
Um, ishtar has all the DBUS vars: address, windowid, and pid -- but what's this
about a cookie?

I didn't see any mention of a cookie monster in my config... ;-/