Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: andrew@pimlott.net (Andrew Pimlott)
Subject: [sup-talk] mime-view hook
Date: Thu, 23 Apr 2009 10:53:36 -0700	[thread overview]
Message-ID: <20090423175336.GX11701@pimlott.net> (raw)
In-Reply-To: <1240448213-sup-1757@junction.es.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


  parent reply	other threads:[~2009-04-23 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  1:11 Jon Dugan
2009-04-23 12:47 ` William Morgan
2009-04-23 17:53 ` Andrew Pimlott [this message]
2009-04-23 18:14   ` Jon Dugan
2009-04-23 22:59     ` Andrew Pimlott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090423175336.GX11701@pimlott.net \
    --to=andrew@pimlott.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox