[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2784: remove support for v1 introducer

[Tahoe-LAFS]

#2784: remove support for v1 introducer
--------------------------+----------------------------
 Reporter:  warner        |          Owner:  warner
     Type:  task          |         Status:  new
 Priority:  normal        |      Milestone:  eventually
Component:  code-network  |        Version:  1.11.0
 Keywords:                |  Launchpad Bug:
--------------------------+----------------------------
 In Tahoe-LAFS-1.10.0 (May 2013), we created a new Introducer protocol
 which allows nodes to publish signed, extensible, dictionary-based
 announcements. Servers are known by their !Ed25519 verifying key, rather
 than their Foolscap TubID (a hash of a TLS certificate).

 To avoid a grid-wide "flag day", all three moving pieces (the sending
 client, the Introducer, and the receiving client) smoothly tolerate old-
 style "v1" messages, and peers which don't know how to speak the v2
 protocol. New clients who discover they're talking to an old Introducer
 will send v1 messages instead of v2. New introducers who receive v1
 messages from old clients will deliver them as unsigned v2 messages to new
 clients, and as v1 messages to old clients.

 Now that 1.10.1 has been available for three years, it's time to remove
 support for the v1 protocol. This will delete maybe 30% of the code from
 `src/allmydata/introducer/`. Clients will unconditionally send and expect
 v2 messages, and the Introducer will only enable v2-capable clients to
 connect and subscribe to hear announcements.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2784>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage