[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #24010 [Core Tor/Torflow]: Make bandwidth authorities use DNS, not IP addresses
#24010: Make bandwidth authorities use DNS, not IP addresses
------------------------------+------------------------
Reporter: teor | Owner: aagbsn
Type: defect | Status: new
Priority: High | Milestone:
Component: Core Tor/Torflow | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: #21394 | Points: 1
Reviewer: | Sponsor:
------------------------------+------------------------
Comment (by teor):
Replying to [comment:5 micah]:
> This strikes me as adding a potentially fragile layer to an already
teetering edifice.
>
> …
>
> I get the point of doing this, but I am not convinced that this should
be the role of bandwidth scanners. Bandwidth scanners should be simply
testing the speed of the network, and nothing else. Its already overly
complicated, even for that one task. I think DNS reachability tests are
important, and the problem does need to be fixed, but I wonder if this
should be done some other way. Perhaps in the client itself? I am unsure.
If the role of bandwidth scanners is to measure bandwidth *as clients
experience it*, then using at least some DNS is appropriate.
We could use a mix of DNS and IP, because that's what clients do. And if
we use a CDN as the server, it will need DNS.
Maybe clients should give up on timed out circuits faster, I opened #24022
for this.
Also, exits can check their own DNS (#24014), but judging what is a slow
resolve is hard, because it needs a comparison to other exits.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24010#comment:6>
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