Reject routerstatuses with orport==0

These could only arrive in error, and might be an attempt to trigger #6690 (moved). Nobody legit can generate them now; we shouldn't start accepting them without more design, I think.

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified needs-proposal priority::medium resolution::wontfix severity::normal status::closed tor-dirauth type::defect labels

Sounds good to me.

Could plausibly be an 0.2.4 thing, since enough authorities will be running it soon enough as it is.

Apologies for not responding promptly to my previous bug submission (bug 6690), but after upgrading to .20 I no longer have this and tor has been running (almost) non-stop for over a week, so I presume whatever it was, it was cleared with the new version.

Hope that helps, but I'll follow this bug closely from now on if you need more info.

Trac:
Username: mr-4

Trac:
Keywords: N/A deleted, needs-proposal added

Trac:
Keywords: needs-proposal deleted, needs-proposal tor-auth added

Trac:
Component: Tor Directory Authority to Tor

Turns out that tor-auth is for directory authority so make it clearer with tor-dirauth

Trac:
Keywords: needs-proposal tor-auth deleted, needs-proposal, tor-dirauth added

It's not clear what it would even mean to "reject" these. Not count votes including them? That would mess up the voting algorithm.

Trac:
Severity: N/A to Normal
Sponsor: N/A to N/A
Reviewer: N/A to N/A
Status: new to closed
Resolution: N/A to wontfix

closed

moved to tpo/core/tor#6716 (closed)