Opened 10 years ago

Closed 9 years ago

#1602 closed task (wontfix)

TorStatus should use Tordnsel instead of its own

Reported by: phobos Owned by: karsten
Priority: Medium Milestone:
Component: TorStatus Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I think torstatus still uses its own "tor check" variant. We should make it use the tordnsel instead (e.g. via fetching the list of current IP addresses from the bulk exitlist, and comparing locally).

Child Tickets

Change History (7)

comment:1 Changed 10 years ago by karsten

Component: WebsiteMetrics
Owner: changed from phobos to karsten

I'm reassigning this task to the Metrics component, because I'm going to extend metrics.tpo to have some TorStatus functionality. But I doubt we want to copy the TorCheck functionality there. Is that correct?

phobos, can we close this task?

comment:2 Changed 10 years ago by karsten

Resolution: wontfix
Status: newclosed

Closing, because it's not relevant for metrics-web.

comment:3 Changed 10 years ago by arma

Resolution: wontfix
Status: closedreopened

Should we make a new torstatus component for these tickets? It seems silly to close a good bug report just because you have another piece of software that you're working on instead. Torstatus is the software that many users use right now, and we have known bugs on it. We should point volunteers at this set of bugs (among many other things).

comment:4 Changed 10 years ago by karsten

Well, I don't think our Trac is the right place to hold TorStatus bugs, because we don't maintain TorStatus. But I wouldn't mind making a new component and re-assigning the tickets. What I do mind about is having them assigned to the Metrics component and to me, because there's no way for me to make progress and solve these tickets.

Shall I create a component and re-assign the tickets?

comment:5 Changed 9 years ago by karsten

Component: MetricsTorStatus
Milestone: Tor Status Deployment

Reassigning to TorStatus, so that the new Django implementation can take this into account from the beginning.

comment:6 Changed 9 years ago by atagar

This is a simple check and TorStatus should already have the data it needs to make this determination. Why should we query an external service? It seems like this adding an extra network burden and dependency without any benefit to TorStatus.

comment:7 Changed 9 years ago by karsten

Resolution: wontfix
Status: reopenedclosed

The metrics database does not contain exit lists.

But on second thought, the new TorStatus shouldn't have to worry about the functionality that's already implemented in TorCheck. We could as well add a link to TorCheck. Or leave it out entirely.


Note: See TracTickets for help on using tickets.