mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-27 13:53:31 +01:00
Add TROVE-2019-001 to changelog for 0.3.4.11
This commit is contained in:
parent
ebda5be955
commit
c41fc1b261
14
ChangeLog
14
ChangeLog
@ -1,5 +1,17 @@
|
||||
Changes in version 0.3.4.11 - 2019-02-21
|
||||
Tor 0.3.4.11 is the third stable release in its series.
|
||||
Tor 0.3.4.11 is the third stable release in its series. It includes
|
||||
a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
|
||||
later. All Tor instances running an affected release should upgrade to
|
||||
0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
|
||||
|
||||
o Major bugfixes (cell scheduler, KIST, security):
|
||||
- Make KIST consider the outbuf length when computing what it can
|
||||
put in the outbuf. Previously, KIST acted as though the outbuf
|
||||
were empty, which could lead to the outbuf becoming too full. It
|
||||
is possible that an attacker could exploit this bug to cause a Tor
|
||||
client or relay to run out of memory and crash. Fixes bug 29168;
|
||||
bugfix on 0.3.2.1-alpha. This issue is also being tracked as
|
||||
TROVE-2019-001 and CVE-2019-8955.
|
||||
|
||||
o Minor features (geoip):
|
||||
- Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
|
||||
|
@ -1,5 +0,0 @@
|
||||
o Major bugfixes (cell scheduler, KIST):
|
||||
- Make KIST to always take into account the outbuf length when computing
|
||||
what we can actually put in the outbuf. This could lead to the outbuf
|
||||
being filled up and thus a possible memory DoS vector. TROVE-2019-001.
|
||||
Fixes bug 29168; bugfix on 0.3.2.1-alpha.
|
Loading…
Reference in New Issue
Block a user