[PATCH] accept SOCKS request over the mux socket

[Jim Knoble]

On 2009-03-12 19:51, William Ahern wrote:

: The way I implemented it was I re-wrote the the -L and -R parser to be
: more generic, using a small state machine rather than ad-hoc string
: parsing. The most straight-forward syntax would be to require domain
: paths to be between braces; then there's no conflict (unless your path
: contains brances, but you can escape those), and you don't even
: necessarily need to require absolute paths, because the brace syntax
: can bootstrap you into a new syntax domain.  For instance:
: 
:       -R[/tmp/remote-foo]:[/tmp/local-bar]

This is interesting.  Salvo had proposed using curly braces '{' and '}'
for this, which may be necessary, as IPv6 addresses are curently allowed
to be inside square brackets '[' and ']'.  Haven't looked at the code,
though.

: Or perhaps:
: 
:       -R[unix://some/relative/path/remote-foo]:[unix:///tmp/local-bar]

Aha.  Thanks, William, for pointing out what I missed: the possibility
of relative paths for the remote end.

This is very interesting, and obviously URI-style specifiers are
relatively commonplace these days.  I would get rid of the '//' after
the ':', as it is supposed to denote a host, but with Unix domain
sockets, the host is implied to be one of the hosts at either end of the
SSH connection.  Thus:

    -R[unix:some/relative/path/remote-foo]:[unix:/tmp/local-bar]

should be sufficient.  I don't mind the extra typing associated with the
square brackets and the URI-style specifier, as i suspect this usage
wouldn't be terribly commonplace anyway.  It also allows square brackets
to be used without conflicting with the optional square brackets around
IPv6 addresses.  I'm in favor of this.

-- 
jim knoble  |  jmknoble at pobox.com  |  http://www.pobox.com/~jmknoble/
(GnuPG key ID: C6F31FFA  >>>>>>  http://www.pobox.com/~jmknoble/keys/ )
(GnuPG fingerprint: 99D8:1D89:8C66:08B5:5C34::5527:A543:8C33:C6F3:1FFA)