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

[tor-bugs] #11487 [FTE]: FTEproxy should (maybe) select the regex on each Bridge line

#11487: FTEproxy should (maybe) select the regex on each Bridge line
-----------------------+------------------------
 Reporter:  infinity0  |          Owner:  kpdyer
     Type:  defect     |         Status:  new
 Priority:  major      |      Milestone:
Component:  FTE        |        Version:
 Keywords:             |  Actual Points:
Parent ID:             |         Points:
-----------------------+------------------------
 Kevin thinks it would be nice to have the FTE regex specified on the
 Bridge line. However, I am confused by the subsequent discussion we had.

 I originally suggested this, because I thought each server has their own
 regex-pair (one for reading, writing), sort of like a scramblesuit shared-
 secret. Then, each client needs a separate regex-pair, per Bridge line.

 However, there is apparently a negotiation step to determine the actual
 regex-pair used:

 18:50:01 <kpdyer_> the first upstream message is always a message encoded
 with some regex and contains a negotiation message
 18:50:16 <kpdyer_> that message contains the exact upstream/downstream
 regexs that will be used for the session

 In this case, if the negotiation happens *independently* of what the
 Bridge is, then

 a) what does the command-line regex mean? the regex for the initial
 negotiation message?
 b) it would be *inappropriate* to set this on the Bridge line, in which
 case please close this ticket as invalid.

 It would be more appropriate to tell the user to edit their
 ClientTransportPlugin line (the current behaviour), since the regex that
 avoids blocking would be *dependent* on their own network, and *not* the
 Bridges that they want to connect to. Or even better, try multiple initial
 regexes and use the one that works.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11487>
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