Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Tor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Container Registry
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
Core
Tor
Commits
23820a39
Commit
23820a39
authored
7 years ago
by
Nick Mathewson
Browse files
Options
Downloads
Patches
Plain Diff
forward-port the 0.3.2.4-alpha changelog.
parent
e03a6369
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
ChangeLog
+101
-0
101 additions, 0 deletions
ChangeLog
with
101 additions
and
0 deletions
ChangeLog
+
101
−
0
View file @
23820a39
Changes in version 0.3.2.4-alpha - 2017-11-08
Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
It fixes several stability and reliability bugs, especially including
a major reliability issue that has been plaguing fast exit relays in
recent months.
o Major bugfixes (exit relays, DNS):
- Fix an issue causing DNS to fail on high-bandwidth exit nodes,
making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
identifying and finding a workaround to this bug and to Moritz,
Arthur Edelstein, and Roger for helping to track it down and
analyze it.
o Major bugfixes (scheduler, channel):
- Stop processing scheduled channels if they closed while flushing
cells. This can happen if the write on the connection fails
leading to the channel being closed while in the scheduler loop.
Fixes bug 23751; bugfix on 0.3.2.1-alpha.
o Minor features (logging, scheduler):
- Introduce a SCHED_BUG() function to log extra information about
the scheduler state if we ever catch a bug in the scheduler.
Closes ticket 23753.
o Minor features (removed deprecations):
- The ClientDNSRejectInternalAddresses flag can once again be set in
non-testing Tor networks, so long as they do not use the default
directory authorities. This change also removes the deprecation of
this flag from 0.2.9.2-alpha. Closes ticket 21031.
o Minor features (testing):
- Our fuzzing tests now test the encrypted portions of v3 onion
service descriptors. Implements more of 21509.
o Minor bugfixes (directory client):
- On failure to download directory information, delay retry attempts
by a random amount based on the "decorrelated jitter" algorithm.
Our previous delay algorithm tended to produce extra-long delays
too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
o Minor bugfixes (IPv6, v3 single onion services):
- Remove buggy code for IPv6-only v3 single onion services, and
reject attempts to configure them. This release supports IPv4,
dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
stack v3 single onion services. Fixes bug 23820; bugfix
on 0.3.2.1-alpha.
o Minor bugfixes (logging, relay):
- Give only a protocol warning when the ed25519 key is not
consistent between the descriptor and microdescriptor of a relay.
This can happen, for instance, if the relay has been flagged
NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
o Minor bugfixes (manpage, onion service):
- Document that the HiddenServiceNumIntroductionPoints option is
0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
bugfix on 0.3.2.1-alpha.
o Minor bugfixes (memory leaks):
- Fix a minor memory leak at exit in the KIST scheduler. This bug
should have no user-visible impact. Fixes bug 23774; bugfix
on 0.3.2.1-alpha.
- Fix a memory leak when decrypting a badly formatted v3 onion
service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
o Minor bugfixes (onion services):
- Cache some needed onion service client information instead of
constantly computing it over and over again. Fixes bug 23623;
bugfix on 0.3.2.1-alpha.
- Properly retry HSv3 descriptor fetches when missing required
directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
o Minor bugfixes (path selection):
- When selecting relays by bandwidth, avoid a rounding error that
could sometimes cause load to be imbalanced incorrectly.
Previously, we would always round upwards; now, we round towards
the nearest integer. This had the biggest effect when a relay's
weight adjustments should have given it weight 0, but it got
weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
- When calculating the fraction of nodes that have descriptors, and
all nodes in the network have zero bandwidths, count the number of
nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
- Actually log the total bandwidth in compute_weighted_bandwidths().
Fixes bug 24170; bugfix on 0.2.4.3-alpha.
o Minor bugfixes (relay, crash):
- Avoid a crash when transitioning from client mode to bridge mode.
Previously, we would launch the worker threads whenever our
"public server" mode changed, but not when our "server" mode
changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
o Minor bugfixes (testing):
- Fix a spurious fuzzing-only use of an uninitialized value. Found
by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
- Test that IPv6-only clients can use microdescriptors when running
"make test-network-all". Requires chutney master 61c28b9 or later.
Closes ticket 24109.
Changes in version 0.3.2.3-alpha - 2017-10-27
Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
numerous small bugs in earlier versions of 0.3.2.x, and adds a new
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment