-
tor (0.4.1.5-1) unstable; urgency=medium
* New upstream version; upload 0.4.1.x to unstable.
* Fix three typos in README.Debian.
* Avoid setting DEB_HOST_ARCH_OS in debian/rules as that should be
pre-initialized nowadays.
* tor-geoipdb: change from priority extra to optional as the former is
obsolete.
* Set Standards-Version to 4.4.0.
* The fix for #930113, runit support, added an /etc/tor/conf to
set the ulimit -n when run under runit. That directory is a bad place.
It confuses users, nowhere is it apparent that only runit cares about that
directory and that e.g. sysV or systemd don't. Get rid of that
directory and the MAX_FILEDESCRIPTORS file in it and set a reasonable
default in the runit script if MAX_FILEDESCRIPTORS is not already set.
-- Peter Palfrader <email address hidden> Wed, 21 Aug 2019 09:59:54 +0200
-
tor (0.4.0.5-2) unstable; urgency=medium
* Upload 0.4.0.x tree to unstable.
-- Peter Palfrader <email address hidden> Sat, 13 Jul 2019 16:00:05 +0200
-
tor (0.3.5.8-1) unstable; urgency=medium
* Replace all references to /var/run with /run (closes: #918898).
* New upstream version.
- Includes a fix for a medium-severity security bug:
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.
-- Peter Palfrader <email address hidden> Thu, 21 Feb 2019 21:28:32 +0100
