Pascal Stumpf:
> OK with me.

Anyone to commit?

g

> 
> On Thu, 08 Nov 2018 16:31:00 +0000, George Rosamond wrote:
>> Attached is net/tor backport of tor-0.3.4.9 to 6.4 -stable, mostly due
>> to memory exhaustion issue.
>>
>> Changelog issues include...
>> (https://github.com/torproject/tor/commit/4ac3ccf2863b86e79040dcd6c9568f011887c2be):
>>
>> <quote Changelog>
>>
>> Changes in version 0.3.4.9 - 2018-11-02
>>   Tor 0.3.4.9 is the second stable release in its series; it backports
>>   numerous fixes, including a fix for a bandwidth management bug that
>>   was causing memory exhaustion on relays. Anyone running an earlier
>>   version of Tor 0.3.4.9 should upgrade.
>>
>>   o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
>>     - Fix compilation on ARM (and other less-used CPUs) when compiling
>>       with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
>>
>>   o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
>>     - Make sure Tor bootstraps and works properly if only the
>>       ControlPort is set. Prior to this fix, Tor would only bootstrap
>>       when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
>>       port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
>>
>>   o Major bugfixes (relay, backport from 0.3.5.3-alpha):
>>     - When our write bandwidth limit is exhausted, stop writing on the
>>       connection. Previously, we had a typo in the code that would make
>>       us stop reading instead, leading to relay connections being stuck
>>       indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
>>       on 0.3.4.1-alpha.
>>
>>   o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
>>     - Fix a use-after-free error that could be caused by passing Tor an
>>       impossible set of options that would fail during options_act().
>>       Fixes bug 27708; bugfix on 0.3.3.1-alpha.
>>
>>
>>>> text/x-patch content
> 

Reply via email to