[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 yawning):

 Replying to [comment:1 dcf]:
 > Can you be more specific about the metrics you're looking for? The one I
 can think of is user graphs that are broken down by pluggable transport
 ''and'' geoip, but there aren't graphs like that and they aren't planned:
 #10218.

 That was what I wanted, though karsten's concerns are still valid (See the
 PT component of Sponsor S for why I care about this all of a sudden).

 > If you're just looking for user counts, we already have that. The user
 graphs don't come from counting unique IPs (they used to); they come from
 counting directory requests: see #8462 and https://gitweb.torproject.org
 /metrics-web.git/blob/HEAD:/doc/users-q-and-a.txt and
 https://research.torproject.org/techreports/counting-daily-bridge-
 users-2012-10-24.pdf.
 >
 > I'm a little opposed to adding a custom header, for a few reasons:
 >  * It can be considered a feature that the bridge doesn't know client
 IPs. From the client point of view, "screw your metrics, I want my
 anonymity."
 >  * We don't actually control the reflector code on any platform other
 than Google. When we use a CDN, the CDN just adds whatever headers it
 wants. Actually it seems that CloudFront
 [https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorCustomOrigin.html#RequestCustomIPAddresses
 already adds X-Forwarded-For].
 >  * As I understand it, Tor could be modified to have its clients send a
 NETINFO cell containing the address. That's what we would want to do if
 metrics are really important, because it would generalize across other
 transports.

 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.

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