[tor-bugs] #9204 [Tor Check]: Modularize check.torproject.org

[Tor Bug Tracker & Wiki]

#9204: Modularize check.torproject.org
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:     
     Type:  project    |         Status:  new
 Priority:  normal     |      Milestone:     
Component:  Tor Check  |        Version:     
 Keywords:             |         Parent:     
   Points:             |   Actualpoints:     
-----------------------+----------------------------------------------------
Changes (by tup):

 * cc: dkantola@… (added)


Comment:

 Replying to [comment:6 Sebastian]:
 > The separation of tasks is actually one of the driving fotces behind
 Torbel. It was designed to be modular from the start

 tordnsel was always modular internally, so splitting up tasks that it can
 already do into separate programs/processes should be easy.

 Replying to [comment:8 nickm]:
 > I don't like the notion of using uploaded-from IP to learn a router's
 outgoing IP; it's too fragile, and it's completely simple to spoof.
 Instead, it should look at the address that connections come from when you
 build a circuit through that node to yourself.

 I should add that detecting all the outgoing IPs from multi-homed routers
 was a design goal in tordnsel. If it doesn't work, that's a bug. I don't
 know if this is still a problem, but there's no simple way that I can
 think of for tor to solve it while still allowing the routers on the
 network (binding the outgoing socket to one IP can be defeated by a packet
 filter, middlebox, host OS, etc.).

 Is there any interest in someone (me) adapting the old tordnsel code for
 this ticket and updating it for the current tor? Is tordnsel fundamentally
 broken in design or implementation, or is it just abandoned and nobody
 wants to maintain it?

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