aboutsummaryrefslogtreecommitdiff
path: root/changes/bug40876
diff options
context:
space:
mode:
authorTor CI Release <no-email@torproject.org>2024-12-03 15:48:11 +0000
committerDavid Goulet <dgoulet@torproject.org>2024-12-03 11:10:03 -0500
commit9918acd57b1f0c80ced1c3e95e0bb98ee4e4e854 (patch)
tree0d517d988c095c8bf99573cfa982ad0822d8cd49 /changes/bug40876
parent5567617e3b725f8a99acada48a5855b2150bc0f4 (diff)
downloadtor-9918acd57b1f0c80ced1c3e95e0bb98ee4e4e854.tar.gz
tor-9918acd57b1f0c80ced1c3e95e0bb98ee4e4e854.zip
release: ChangeLog and ReleaseNotes for 0.4.9.1-alpha
Diffstat (limited to 'changes/bug40876')
-rw-r--r--changes/bug408768
1 files changed, 0 insertions, 8 deletions
diff --git a/changes/bug40876 b/changes/bug40876
deleted file mode 100644
index a467cf64c1..0000000000
--- a/changes/bug40876
+++ /dev/null
@@ -1,8 +0,0 @@
- 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.