torproject/torspec
1
0
Fork 0
mirror of https://github.com/torproject/torspec.git synced 2025-02-17 07:10:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Mark proposal 297-safer-protocol-shutdowns.txt as implemented (#27735)

Browse Source
This commit is contained in:
Nick Mathewson 2018-12-11 09:52:35 -05:00
parent 54c3a5f09d
commit 18fcb9ab42
3 changed files with 23 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
proposals/000-index.txt
View File

@ -217,7 +217,7 @@ Proposals by number:
294 TLS 1.3 Migration [DRAFT]
295 Using ADL-GCM for relay cryptography (solving the crypto-tagging attack) [OPEN]
296 Have Directory Authorities expose raw bandwidth list files [OPEN]
297 Relaxing the protover-based shutdown rules [OPEN]
297 Relaxing the protover-based shutdown rules [CLOSED]
298 Putting family lines in canonical form [CLOSED]
@ -249,7 +249,6 @@ Proposals by status:
289 Authenticating sendme cells to mitigate bandwidth attacks
295 Using ADL-GCM for relay cryptography (solving the crypto-tagging attack)
296 Have Directory Authorities expose raw bandwidth list files
297 Relaxing the protover-based shutdown rules [for 0.3.5.x]
ACCEPTED:
188 Bridge Guards and other anti-enumeration defenses
249 Allow CREATE cells with >505 bytes of handshake data
@ -355,6 +354,7 @@ Proposals by status:
283 Move IPv6 ORPorts from microdescriptors to the microdesc consensus [for 0.3.3.x] [in 0.3.3.1-alpha]
284 Hidden Service v3 Control Port
293 Other ways for relays to know when to publish [for 0.3.5] [in 0.4.0.1-alpha]
297 Relaxing the protover-based shutdown rules [for 0.3.5.x] [in 0.4.0.x]
298 Putting family lines in canonical form [for 0.3.6.x] [in 0.4.0.1-alpha]
SUPERSEDED:
112 Bring Back Pathlen Coin Weight

10
proposals/297-safer-protover-shutdowns.txt
View File

@ -2,8 +2,16 @@ Filename: 297-safer-protover-shutdowns.txt
Title: Relaxing the protover-based shutdown rules
Author: Nick Mathewson
Created: 19-Sep-2018
Status: Open
Status: Closed
Target: 0.3.5.x
Implemented-In: 0.4.0.x
IMPLEMENTATION NOTE:
We went with the proposed change in section 2. The "release date" is
now updated by the "make update-versions" target whenever the version
number is incremented. Maintainers may also manually set the "release
date" to the future.
1. Introduction

16
tor-spec.txt
View File

@ -1935,19 +1935,27 @@ see tor-design.pdf.
it should warn its operator that the relay is obsolete.
- When a relay lacks a protocol listed in required-relay-protocols, it
must not attempt to join the network.
should warn its operator as above. If the consensus is newer than the
date when the software was released or scheduled for release, it must
not attempt to join the network.
- When a client lacks a protocol listed in recommended-client-protocols,
it should warn the user that the client is obsolete.
- When a client lacks a protocol listed in required-client-protocols, it
must not connect to the network. This implements a "safe forward
shutdown" mechanism for zombie clients.
- When a client lacks a protocol listed in required-client-protocols,
it should warn the user as above. If the consensus is newer than the
date when the software was released, it must not connect to the
network. This implements a "safe forward shutdown" mechanism for
zombie clients.
- If a client or relay has a cached consensus telling it that a given
protocol is required, and it does not implement that protocol, it
SHOULD NOT try to fetch a newer consensus.
Software release dates SHOULD be automatically updated as part of the
release process, to prevent forgetting to move them forward. Software
release dates MAY be manually adjusted by maintainers if necessary.
Starting in version 0.2.9.4-alpha, the initial required protocols for
clients that we will Recommend and Require are: