| commit | b14bb12e39d3ccb95a9e5d9cf3eda8428c129520 | |
| author | Mike Perry <mikeperry-git@torproject.org> | |
| Thu, 8 Aug 2019 17:49:33 +0000 (8 12:49 -0500) | ||
| committer | Mike Perry <mikeperry-git@torproject.org> | |
| Mon, 12 Aug 2019 19:02:35 +0000 (12 14:02 -0500) | ||
| tree | 67eca6d69a9f104fc9f1430d86d9fc84dee19926 | treesnapshot (tar.gz zip) |
| parent | f6bc9d7c7eff9d50e5499007ea3a742b259e6ff9 | commitdiff |
Bug 31356: Bump protover for new padding machines
By binding the protover numbering to specific padding machines, we can make
our padding negotiation simpler. We probably should have done this in the
first place.
This has the side effect that earlier 0.4.1.x-alpha clients won't negotiate
with 0.4.1.x-stable relays, and 0.4.1.x-stable clients won't negotiate with
earlier 0.4.1.x-alpha relays (or 0.4.0.x relays). Since we don't support
alphas after the stable is released, this is fine, so long as it gets in
before the first stable of 0.4.1.x.
By binding the protover numbering to specific padding machines, we can make
our padding negotiation simpler. We probably should have done this in the
first place.
This has the side effect that earlier 0.4.1.x-alpha clients won't negotiate
with 0.4.1.x-stable relays, and 0.4.1.x-stable clients won't negotiate with
earlier 0.4.1.x-alpha relays (or 0.4.0.x relays). Since we don't support
alphas after the stable is released, this is fine, so long as it gets in
before the first stable of 0.4.1.x.
| src/core/or/protover.c | diffblobblamehistory | |
| src/rust/protover/protover.rs | diffblobblamehistory |