Opened 11 months ago

Last modified 6 days ago

#29650 new project

Rewrite exit scanner to produce exit lists according to new format

Reported by: irl Owned by: metrics-team
Priority: High Milestone:
Component: Metrics/Exit Scanner Version:
Severity: Normal Keywords: metrics-roadmap-2019-q2 exitscanner
Cc: Actual Points:
Parent ID: #29399 Points:
Reviewer: Sponsor:

Description

The current exit scanner is purpose written software using Haskell. It is non-trivial to update this program to run on a modern Debian system and would be easier in the longer term to simply replace.

This task requires the new exit list specification to be completed in #29624.

Expected new features:

  • Written in Python
  • Support for IPv6
  • Support for new exit list format

Features we would like:

  • Cryptographically signed measurement results
  • Archival signatures

Child Tickets

TicketStatusOwnerSummaryComponent
#29624newmetrics-teamNew version of exit list formatMetrics/Exit Scanner
#29651closedmetrics-teamDesign the new exit scanner architectureMetrics/Exit Scanner
#29652closedirlEvaluate the reusability of existing check.tpo applicationMetrics/Exit Scanner
#29653closedmetrics-teamEvaluate the reusability of existing TorDNSEL applicationMetrics/Exit Scanner
#29654newmetrics-teamInitial MVP for new exit scannerMetrics/Exit Scanner

Change History (10)

comment:1 Changed 11 months ago by irl

Component: MetricsMetrics/Exit Scanner

comment:2 Changed 4 months ago by anarcat

gentle ping: we were told two months ago that "This is in our current roadmap. We're going to start in October and expect to be done by end of December". Is this still happening?

thanks!

comment:3 Changed 4 months ago by gaba

Yes. It is in our roadmap and we are going to discuss it in our next metrics team meeting on October 14th.

comment:4 Changed 4 months ago by gaba

Priority: MediumHigh

comment:5 Changed 3 months ago by anarcat

so, what was the result of the discussion? :)

update: gaba told me they were still on course for the "end of december" timeline, thanks!

Last edited 3 months ago by anarcat (previous) (diff)

comment:6 Changed 3 months ago by gaba

that is starting as soon as metrics is wrapping up what they are doing right now

comment:7 Changed 3 months ago by gaba

Keywords: exitscanner added

comment:8 Changed 2 months ago by anarcat

Parent ID: #29399

mark as part of the chiwui retirement project

comment:9 Changed 2 months ago by irl

The existing LDAP groups are 'check' and 'tordnsel'. cf #32553

The new deployment can reuse these groups.

comment:10 Changed 6 days ago by anarcat

update: gaba told me they were still on course for the "end of december" timeline, thanks!

I'm working on the yearly roadmap here and I would love to have a timeline of when we can turn off that host indefinitely. As a reminder, the operating system on chiwui is running Debian 8 "jessie" which has been officially unsupported by the Debian project since june 2018. It's been under life support since, under the unofficial LTS project, which will end, for that release, in June 2020.

We were given a March 2019 deadline first, and this was pushed back twice. I would love to have this finished before the hard deadline of June 2020, but failing that, I *will* be forced to shutdown that server in June 2020, otherwise we'll face more serious issues as the entire platform will be unsupported for security issues.

TL;DR: please, give us a timeline. :)

Note: See TracTickets for help on using tickets.