[tor-bugs] #12585 [Tor]: Implement new option SocksSocket
Tor Bug Tracker & Wiki
blackhole at torproject.org
Thu Jan 8 15:35:58 UTC 2015
#12585: Implement new option SocksSocket
-----------------------------+--------------------------------
Reporter: ioerror | Owner:
Type: enhancement | Status: needs_revision
Priority: normal | Milestone: Tor: 0.2.6.x-final
Component: Tor | Version: Tor: unspecified
Resolution: | Keywords: 026-triaged-1
Actual Points: | Parent ID:
Points: |
-----------------------------+--------------------------------
Comment (by ioerror):
Replying to [comment:45 nickm]:
> Replying to [comment:44 ioerror]:
> > Replying to [comment:43 nickm]:
> > >
> > > Throughout:
> > >
> > > * Looks nice! Much simpler now.
> >
> > Agreed - a lot of refactoring that makes it easier to read!
> >
> > >
> > > - This is probably gonna break on windows: I don't think they have
AF_UNIX, and at least address.c uses AF_UNIX unconditionally. I can clean
it up if you want, or you can if you've got mingw cross-compilation stuff
installed.
> >
> > I think it would be great if anyone with Windows could make this work.
It would remove lots of local firewall issues, I think. I think the proper
way to implement it would be to use a named pipe (
http://msdn.microsoft.com/en-
us/library/windows/desktop/aa365590%28v=vs.85%29.aspx ) and it would
effectively be the same feature.
>
> Not that simple, I'm afraid. Named pipes don't interoperate with
sockets in the way we're using them. You'd need to do some low-level
hacking on the async io layer. (Not impossible, but likely to involve
complexity.)
Ah. That sounds sad.
>
> In other words "Good idea, but a bit tricky. Somebody should open a new
ticket so this one doesn't block on it." ;)
Understood. Ok - so that answers that question - so your point was just to
make sure that Tor will still work on Windows then? I think you are the
best person to help with this Windows stuff - though I'm happy to learn
about the mingw stuff if it is documented somewhere...
>
> [...]
> > In some kind of ideal world, I like the idea of shipping TBB with
Firefox completely sandboxed from making TCP/IP connection on two of our
three platforms. The third one being windows, of course. I guess that
depends on discovering if NamedPipes will work or not.
>
> Same as above wrt "Good idea but a bit tricky. Somebody should open a
new ticket so this one doesn't block on it." ;)
Ok. I think this is a TBB discussion that we can have after this is
merged. I've opened #14132 for torsocks - which in theory, we can use to
test all of these crazy ideas. That is - it should be possible to sandbox
Tor Browser with torsocks in a single line - without patching firefox, if
we suceed with torsocks hacking plans.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12585#comment:47>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list