forward the dbus session?

[Goran Hasse]

In the past it was not a problem to log into a system many times (as the
same user). Now it is a mess! If you start a lot of programs on one seat
and then moves to another system and log in remotly to the first - you get
all sort of problems. Application already started. Locks betwen files, mixed
chaches and other stuff.

example:

(sleep 5 ; DISPLAY=:1 xterm ) & Xnest :1

Then in the xterm window you write  "firefox".

You get: "firefox is already running..."
So you can't get another instans running. Effectivily you have turned
your mutliuser
system into a single user one...

GH

2009/2/14 Ben Lindstrom <mouring at eviladmin.org>:
> Any reason why this has to be an unique feature?  Is there some form
> of authentication cookie or something that needs to be managed?  That
> is really the only reason why X forwarding exists.  Otherwise it could
> also be yet another port tunnel.
>
> - Ben
>
> On Feb 13, 2009, at 5:38 PM, Brian J. Murrell wrote:
>
>> Am I crazy for thinking about forwarding the DBUS session over an ssh
>> connection much like the X session is forwarded?
>>
>> I've proven the concept with socat (to use the unix socket that dbus
>> normally listens on rather than reconfiguring dbus to use a tcp
>> socket)
>> and it works just as expected.
>>
>> Any reason we wouldn't want openssh doing this natively?
>>
>> b.
>>
>> _______________________________________________
>> openssh-unix-dev mailing list
>> openssh-unix-dev at mindrot.org
>> https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
>
> _______________________________________________
> openssh-unix-dev mailing list
> openssh-unix-dev at mindrot.org
> https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
>



-- 
gorhas at gmail.com
Mob: 070-5530148