Re: GEP 3 - Remote activation in bonobo-activation

[Alan Cox <alan redhat com>]

> There are several ways this can be fixed: 
>         * Opening an SSH session to the machine holding the component to
>           be activated, and start the local-per-user bonobo-activation
>           daemon on that machine, so that it activates the component. 
>         * Create a system-wide daemon that listens on a well known port
>           for requests from bonobo-activation clients on other machines.
> 
> 'Scuse my ignorance, but isn't that what xinetd/inetd and company are
> for?

Large numbers of people don't run xinetd/inetd. They expose only the ssh
session for the X desktop (which you could also use to start things
just like real X windows programmers would).

As security becomes more and more important the odds that you'll have any
connectivity beyond the ssh tunnels between client and desktop go down
more and more.

Alan