diff options
author | Roger Dingledine <arma@torproject.org> | 2022-08-09 16:39:26 -0400 |
---|---|---|
committer | Roger Dingledine <arma@torproject.org> | 2022-08-09 16:39:26 -0400 |
commit | d48eaff86d5d2bd0df2b0974abf28652934b5cc6 (patch) | |
tree | 18163a07cb82485d3c145f471a1cbe5e1afaadcb /changes | |
parent | 7b1fffe0ddfb78234bddba4aae5800482d8b01fb (diff) | |
download | tor-d48eaff86d5d2bd0df2b0974abf28652934b5cc6.tar.gz tor-d48eaff86d5d2bd0df2b0974abf28652934b5cc6.zip |
ignore families for L2 guard independence
mike is concerned that we would get too much exposure to adversaries,
if we enforce that none of our L2 guards can be in the same family.
this change set now essentially finishes the feature that commit a77727cdc
was attempting to add, but strips the "_and_family" part of that plan.
Diffstat (limited to 'changes')
-rw-r--r-- | changes/bug40639 | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/changes/bug40639 b/changes/bug40639 index d5ab2e0cb3..d975e9ad22 100644 --- a/changes/bug40639 +++ b/changes/bug40639 @@ -1,5 +1,5 @@ o Major bugfixes (vanguards): - We had omitted some checks for whether our vanguards (second layer - guards from proposal 333) overlapped or came from the same family. - Now make sure to pick each of them to be independent. Fixes bug - 40639; bugfix on 0.4.7.1-alpha. + guards from proposal 333) overlapped. Now make sure to pick each + of them to be independent. Also, change the design to allow them to + come from the same family. Fixes bug 40639; bugfix on 0.4.7.1-alpha. |