From mboxrd@z Thu Jan  1 00:00:00 1970
From: andrew@pimlott.net (Andrew Pimlott)
Date: Thu, 23 Apr 2009 10:53:36 -0700
Subject: [sup-talk] mime-view hook
In-Reply-To: <1240448213-sup-1757@junction.es.net>
References: <1240448213-sup-1757@junction.es.net>
Message-ID: <20090423175336.GX11701@pimlott.net>

On Wed, Apr 22, 2009 at 06:11:40PM -0700, Jon Dugan wrote:
> dumbplumbd listens on port 9937 on your local system for requests.  dumbplumb
> sends requests to dumbplumbd.  ssh port forwarding is used to proxy the two
> together, eg:
> 
> ssh -R 9937:localhost:9937 remotehost

You probably realize this, but...  A well-known port doesn't work for
this, because you need one plumber per display session.  So the SSH
forwarding needs to use the right plumber on this end and establish a
corresponding session on the other end.

The obvious model for this is SSH agent forwarding.  You'd have a
PLUMBER_SOCK variable containing the path to a unix socket, and ssh
would create a unix socket on the other end, forward it there, and set a
new PLUMBER_SOCK variable.  The obstacle is, the SSH developers haven't
shown any interest in making the SSH agent forward mechanism availble to
others.  See for example

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=294148

If you don't do this, you'll have plumbers stepping on each other, or
you'll have to manage ports manually.

Andrew