[tor-bugs] #13171 [meek]: meek's reflector should forward the client's IP address/port to the bridge.

[Tor Bug Tracker & Wiki]

#13171: meek's reflector should forward the client's IP address/port to the bridge.
-----------------------------+-----------------
     Reporter:  yawning      |      Owner:  dcf
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  meek         |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by dcf):

 Replying to [comment:3 yawning]:
 > Hmm, all valid reasons for not using a custom header.  I would guess
 that most CDN platforms would set X-Forwarded-For, and if we wanted to use
 that information in meek-server, adding the header in the GAE go code
 would be trivial.  I'll think more about #10218.

 You're probably right that all CDNs make the information available
 somehow. You don't want to use the client port, even if it is available,
 because a stream is made of multiple HTTP requests and the port is
 changing all the time. You would want to derive the port from the session-
 ID somehow.

 If you dig through Psiphon's history on meek-client,
  * https://bitbucket.org/psiphon/psiphon-circumvention-system/history-
 node/default/go/meek-client/meek-client.go
 you can see that they added support for sending an encrypted cookie
 through the CDN to the server, I believe for similar reasons:
  * https://bitbucket.org/psiphon/psiphon-circumvention-system/diff/go
 /meek-client/meek-client.go?diff2=6d906a57c6fb

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13171#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online