[tor-dev] Proposal xxx: Further SOCKS5 extensions (Was Pluggable transport SOCKS5 extensions)

[Yawning Angel]

On Sat, 8 Mar 2014 09:08:06 -0500
David Goulet <dgoulet at ev0ke.net> wrote:

[snippity]
> > > I can see one use for having custom keys along with a name space
> > > which is to having a way to identify the SOCKS connection on the
> > > control port for knowing in which country the exit is for
> > > instance (or whatever info you need). The source port can be use
> > > for that but for an external client not knowing it, it might be
> > > interesting to be able to ask the control port "What's the exit
> > > node of <INSERT_KEY> SOCKS connection".
> > 
> > Is a custom key needed for this?  The query you used as an example
> > could just as easily be done without any SOCKS extensions as "What's
> > the exit node of <Insert Source Address/Port> SOCKS connection"
> > couldn't it?
> 
> That would work (and works) if you know the source port and for that
> you basically need to be the client who made that request unless you
> happily parse netstat :P. So here is an exemple, I have 5 differents
> apps using the SOCKSPort, I might be interested in asking tor daemon
> what's the exit point of my app number 3? That could be interesting to
> ask the control port something like "Give me exit relay country for
> SOCKS port myapp3.insert.namespace.here".
> 
> Not sure that it's or could be possible but maybe just something to
> think about.

Ah I see.  I'd feel better about the namespace and "how easy would this
be to implement" if this sort of thing was done via a separate key/value
pair. So in addition to the keys I specified we could reserve "appID"
as a key for this (Eg: "appid"/"tbb<SessionID>", "timb<SessionID>",
etc).  With prefixing the keys, the arg processing code for everything
needs to be appid aware (optional thing should be optional, and easy
to ignore).

Regards,

-- 
Yawning Angel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20140308/3e481c59/attachment.sig>