Links to IP addresses in same /24 are broken

When a result is negative but there are IP addresses of relays in the same /24, we're printing out links to those searches. However, those searches are currently broken since moving ExoneraTor to Tor Metrics. I'm not fixing this right away, because I'd like to get the legacy/trac#27234 (moved) changes merged first. Should be okay to wait another week.

added component::metrics/exonerator in Legacy / Trac owner::metrics-team in Legacy / Trac priority::medium in Legacy / Trac resolution::fixed in Legacy / Trac severity::normal in Legacy / Trac status::closed in Legacy / Trac type::defect in Legacy / Trac labels

Please review commit b8dbfe1 in my task-27266 branch.

Trac:
Status: new to needs_review

Ok. Looks good to me.

Trac:
Status: needs_review to merge_ready

Great! Please also take a look at the two new commits in that same branch that prepare the release, and check whether the following pre-release tarball looks okay to you:

https://people.torproject.org/~karsten/volatile/exonerator-3.0.1-pre0.tar.gz

Trac:
Status: merge_ready to needs_review

Looks good to me mostly, although a certificate has changed with no explanation as to why.

Trac:
Status: needs_review to merge_ready

Thanks for checking! I updated the certificate, because the old certificate had expired. I'm doing that every three months and copying over the certificate to the other code bases whenever putting out the next release. That's why.

Merged to master, tagged, released, deployed. Do we want to put out a release announcement? I guess not, but I don't feel strongly. Leaving open for the announcement decision only.

Ok. We should discuss in Mexico how these certificates are handled and how to bootstrap trust in them. It may be that when we come to automating some deployments we want to verify the signatures but this would need to be done automatically.

I think a quick mail would be good, especially as this fixes a bug that was raised by a user, not just found internally.

Replying to irl:

Ok. We should discuss in Mexico how these certificates are handled and how to bootstrap trust in them. It may be that when we come to automating some deployments we want to verify the signatures but this would need to be done automatically.

Sounds good to me.

I think a quick mail would be good, especially as this fixes a bug that was raised by a user, not just found internally.

Ah, I sent the last announcement, so I should be sending this one, too. Done.

Closing. Thanks!

Trac:
Status: merge_ready to closed
Resolution: N/A to fixed

closed

mentioned in issue legacy/trac#27312 (moved)

moved from legacy/trac#27266 (moved)

added Bug label and removed 1 deleted label

removed 1 deleted label