diff options
| author | David Goulet <dgoulet@torproject.org> | 2023-11-09 09:10:58 -0500 |
|---|---|---|
| committer | David Goulet <dgoulet@torproject.org> | 2023-11-09 09:10:58 -0500 |
| commit | 525a1cfb70c45055aaf42fc695aa24befc35aec7 (patch) | |
| tree | 01b48973338f635e5b3d891f92d444505f02011c /changes | |
| parent | 54e37a013bf5a7c334f9c446467719abf46e449f (diff) | |
| parent | 6df27ae9537dbc67846a5025945636b489674f0d (diff) | |
| download | tor-525a1cfb70c45055aaf42fc695aa24befc35aec7.tar.gz tor-525a1cfb70c45055aaf42fc695aa24befc35aec7.zip | |
Merge branch 'maint-0.4.8'
Diffstat (limited to 'changes')
| -rw-r--r-- | changes/bug40876 | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/changes/bug40876 b/changes/bug40876 new file mode 100644 index 0000000000..a467cf64c1 --- /dev/null +++ b/changes/bug40876 @@ -0,0 +1,8 @@ + o Major bugfixes (guard usage): + - When Tor excluded a guard due to temporary circuit restrictions, + it considered *additional* primary guards for potential usage + by that circuit. This could result in more than the specified number + of guards (currently 2) being used, long-term, by the tor client. + This could happen when a Guard was also selected as an Exit node, + but it was exacerbated by the Conflux guard restrictions. Both + instances have been fixed. Fixes bug 40876; bugfix on 0.3.0.1-alpha. |