Prop 312: 3.2.3 Limit Directory Authority Addresses to Address and ORPort

For security reasons, directory authorities only use addresses that are explicitly configured in their torrc. Since local interface addresses are implicit, and may depend on DHCP, directory authorities do not use this address resolution method (or any of the other, lower-priority address resolution methods).

See proposal 312, section 3.2.3, directory authority case: https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n388

Trac:
Parent Ticket: legacy/trac#33049 (moved)

added 044-deferred in Legacy / Trac component::core tor/tor in Legacy / Trac parent::33049 in Legacy / Trac points::1 in Legacy / Trac priority::medium in Legacy / Trac prop312 in Legacy / Trac security-low in Legacy / Trac severity::normal in Legacy / Trac sponsor::55-must in Legacy / Trac status::assigned in Legacy / Trac tor-dirauth in Legacy / Trac type::enhancement in Legacy / Trac labels

Un-assign myself from future Sponsor 55 tasks.

Trac:
Owner: teor to N/A

I think we should do legacy/trac#33237 (moved) and legacy/trac#33239 (moved), but they aren't urgent, so we should leave them until the end of the project.

Trac:
Keywords: N/A deleted, security-low added

Add 044-must to all security tickets in 0.4.4

Trac:
Keywords: N/A deleted, 044-must added

Trac:
Keywords: 044-must deleted, N/A added

Bulk-remove tickets from 0.4.4. Add the 044-deferred label to them.

Trac:
Keywords: N/A deleted, 044-deferred added
Milestone: Tor: 0.4.4.x-final to Tor: unspecified

Bulk-move prop311 and prop312 to 0.4.5

Trac:
Milestone: Tor: unspecified to N/A

changed time estimate to 8h

mentioned in issue legacy/trac#33049 (moved)

moved from legacy/trac#33239 (moved)

mentioned in issue #33049 (closed)

added Feature + 1 deleted label and removed 1 deleted label

added Icebox label

added Authority Deferred + 1 deleted label and removed 1 deleted label

changed milestone to %Tor: 0.4.5.x-freeze

mentioned in issue #33237 (closed)

Would it work if on a DirAuth that both ORPort and Address have to be set?

Can I exclude this check for "TestingTorNetwork"?

Address and ORPort have different meaning.

The Address is the one you consider your relay accessible from so the one that will be published in the descriptor.

The ORPort is where to listen on. If no Address exists, then it is used as the "primary" IP. And if no address is used with that option, address discovery continues onto the network interface and then local hostname DNS query.

assigned to @dgoulet

mentioned in merge request !76 (merged)

added Doing label and removed Icebox label

closed via merge request !76 (merged)

added Security label and removed 1 deleted label