dir-spec.txt: Clarify Exit flag

The Exit flag explanation is in dir-spec.txt is misleading. Attached is a patch for clarification.

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified priority::low resolution::worksforme severity::normal status::closed type::enhancement labels

Trac:
clarify-exit-flag.patch

Where are you getting the "bandwidth is at least 4k" limit from? I am not finding it in dirserv.c.

Trac:
Milestone: N/A to Tor: 0.2.5.x-final
Status: new to needs_review

Replying to nickm:

Where are you getting the "bandwidth is at least 4k" limit from? I am not finding it in dirserv.c.

I have to admit that I blindly took it for granted from line 1714 in dir-spec.txt. I just remember that the exit flag is not given to a low bandwidth node regardless of its exit policy - which I think is very confusing and should be documented. But I don't know where "low bandwidth" is defined exactly.

Trac:
Keywords: N/A deleted, 025-triaged added

Trac:
Status: needs_review to needs_revision

Trac:
Keywords: 025-triaged deleted, N/A added
Milestone: Tor: 0.2.5.x-final to Tor: 0.2.6.x-final

I'll take an updated patch here if somebody makes one that's accurate.

Trac:
Milestone: Tor: 0.2.6.x-final to Tor: 0.2.???

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

The description has been updated at least once since this ticket was opened.

Trac:
Resolution: N/A to worksforme
Reviewer: N/A to N/A
Sponsor: N/A to N/A
Severity: N/A to Normal
Status: needs_revision to closed

closed

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