Opened 10 years ago

Closed 10 years ago

#1767 closed task (fixed)

Project: Integrate exit scanner improvements

Reported by: nickm Owned by: mikeperry
Priority: Medium Milestone: Deliverable-Sep2010
Component: Core Tor/Torflow Version:
Severity: Keywords:
Cc: phobos Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


We have a september 30 deliverable currently listed as: "Exit scanner - in process, still undergoing more work, has a Google Summer of Code student working on it now"

Step one here is to get more clarity about the final deliverables, and the Sep 30 deliverables. Are they just a matter of integrating the GSoC improvements, or is more needed?

Child Tickets:
No results

Child Tickets

Change History (9)

comment:1 Changed 10 years ago by mikeperry

John's GSoC code has been merged into master and is running on both my machine and his. We both should be emailing results to the exit scanner list.

Does that mean this ticket can be closed for the Sept 2010 deliverable?

comment:2 Changed 10 years ago by phobos

Do we trust the exit scanner to provide actionable items at this point? If not, when?

comment:3 Changed 10 years ago by mikeperry

Do you mean automatically actionable, as in the directory authorities BadExit nodes by themselves? Probably not. But we've BadExit flagged several nodes based on the output of John's scanner. The signal to noise ratio and the quality of results does seem to have improved due to John's work.

My scanner is set to email, but it is only 55% through the scan right now. It started 6 days ago, so hopefully we'll see the emails from my scans in another week.

comment:4 Changed 10 years ago by asn


comment:5 Changed 10 years ago by mikeperry

Ok. For the record, that scan finished on Sept 8. So the scan duration is manageable, and it will finish. We can also tweak some params to make it shorter (or at least document them).

For the end of Sept, my goal is to improve snakeinspector's output filtering. Right now, the filtering parameters only apply during the scan. If I make them so they can be applied to snakeinspector after a run, I can tweak them a bit lower to reduce the noise of this most recently completed scan I have on disk (that used John's code).

I also need to check the cron script I wrote into git, and make sure it is working right. It should have emailed my results on Sept 8 but I didn't see the mail. May be a bug in there.

I think that these two things should put us in good shape for declaring this deliverable done, because the scanner should run and email, and not be noisy at that point.

comment:6 Changed 10 years ago by arma

I'd say if we have it actually sending mail -- reliably sending mail in a periodic fashion -- and we find each mail interesting, then we'll be in good shape.

comment:7 Changed 10 years ago by arma

Component: - Select a componentTorflow

So, "yes, sounds great"

Note: See TracTickets for help on using tickets.