Drop AlternativeHSAuthority and friends

We haven't had a notion of an HSAuthority since we dropped the v0 hidden service descriptor design completely back in 0.2.2. (See legacy/trac#10841 (moved) for more.) Specifically, in 0.2.2 or later, neither clients nor relays publish anything resembling a v0 hidden service descriptor, and "HS authorities" have nothing to do.

That said, we should drop the vestigial AlternativeHSAuthority option, since it has apparently has misled some folks into thinking that we do have HS authorities. (See legacy/trac#10722 (moved).)

changed milestone to %Tor: 0.2.5.x-final in legacy/trac

added component::core tor/tor in Legacy / Trac docs in Legacy / Trac milestone::Tor: 0.2.5.x-final in Legacy / Trac parent::10841 in Legacy / Trac priority::low in Legacy / Trac resolution::fixed in Legacy / Trac status::closed in Legacy / Trac tor-client in Legacy / Trac tor-hs in Legacy / Trac type::defect in Legacy / Trac labels

Trac:
Summary: Drop AlternatieHSAuthority and friends to Drop AlternativeHSAuthority and friends

Trac:
Component: - Select a component to Tor

Trac:
Description: We haven't had a notion of an HSAuthority since we dropped the v0 hidden service descriptor design completely back in 0.2.2. (See legacy/trac#10849 (moved) for more.) Specifically, in 0.2.2 or later, neither clients nor relays publish anything resembling a v0 hidden service descriptor, and "HS authorities" have nothing to do.

That said, we should drop the vestigial AlternativeHSAuthority option, since it has apparently has misled some folks into thinking that we do have HS authorities. (See legacy/trac#10722 (moved).)

to

We haven't had a notion of an HSAuthority since we dropped the v0 hidden service descriptor design completely back in 0.2.2. (See legacy/trac#10841 (moved) for more.) Specifically, in 0.2.2 or later, neither clients nor relays publish anything resembling a v0 hidden service descriptor, and "HS authorities" have nothing to do.

That said, we should drop the vestigial AlternativeHSAuthority option, since it has apparently has misled some folks into thinking that we do have HS authorities. (See legacy/trac#10722 (moved).)

Trac:
Parent: N/A to legacy/trac#10841 (moved)

This part is done in "bug10881" in my public repo. Please review?

Trac:
Status: new to needs_review
Cc: N/A to karsten

Looks good.

While looking through the changes, I found this part in the man page close to the changes in your bug10881 branch that isn't correct anymore since legacy/trac#10758 (moved). If you want a new ticket or branch for this, let me know.

diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index e66fad2..36c1e3e 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -331,8 +331,8 @@ GENERAL OPTIONS
     and port, with the specified key fingerprint. This option can be repeated
     many times, for multiple authoritative directory servers. Flags are
     separated by spaces, and determine what kind of an authority this directory
-    is. By default, every authority is authoritative for current ("v2")-style
-    directories, unless the "no-v2" flag is given. If the "v1" flags is
+    is. By default, an authority is not authoritative for any directory style
+    or version, unless one or more flags are given. If the "v1" flags is
     provided, Tor will use this server as an authority for old-style (v1)
     directories as well. (Only directory mirrors care about this.)
     Tor will use this authority as a bridge authoritative directory if the

Okay. Merged this, added that. Also changed "If the "v1" flags is" to "If the "v1" flag is".

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

closed

moved from legacy/trac#10881 (moved)

added Bug label and removed 1 deleted label

added Client + 1 deleted label and removed 1 deleted label

added Documentation label and removed 1 deleted label