[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #17142 [Tor]: allow remote portforwarding on exit nodes

#17142: allow remote portforwarding on exit nodes
-----------------------------+---------------------------------
     Reporter:  iwtcitp      |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  minor        |  Milestone:  Tor: very long term
    Component:  Tor          |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+---------------------------------

Comment (by yawning):

 So, ignoring the "this would be a legal nightmare" and "this would be a
 nightmare to make robust against people being malicious" components for
 the moment (though I think that those objections are enough to make it
 unlikely that this gets done)...  This would be a massive amount of code.
 I suppose the "easy" way would be to allow backward RELAY_BEGINS and use
 the single circuit constructed to register the mapping for subsequent
 traffic...

 IMO efforts would be better directed to making HSes easier to run (Eg:
 #6411), and making tor easier to bundle (though I don't think
 forking/execing a tor instance is particularly hard, apart from iOS).

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17142#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs