Change log for tor package in Ubuntu

175 of 107 results
Published in eoan-release on 2019-04-18
Published in disco-release on 2019-03-05
Deleted in disco-proposed (Reason: moved to release)
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

Available diffs

Superseded in disco-release on 2019-03-05
Deleted in disco-proposed on 2019-03-07 (Reason: moved to release)
tor (0.3.5.7-1) unstable; urgency=medium

  * New upstream version, upload 0.3.5.x tree to unstable.

 -- Peter Palfrader <email address hidden>  Tue, 08 Jan 2019 09:22:13 +0100

Available diffs

Superseded in disco-release on 2019-01-09
Deleted in disco-proposed on 2019-01-11 (Reason: moved to release)
tor (0.3.4.9-7) unstable; urgency=medium

  * setup-onion-service: mark as flaky

 -- Peter Palfrader <email address hidden>  Fri, 07 Dec 2018 18:21:40 +0100

Available diffs

Published in trusty-updates on 2018-11-26
Published in trusty-security on 2018-11-26
tor (0.2.4.27-1ubuntu0.1) trusty-security; urgency=medium

  * SECURITY UPDATE: DoS (client crash) via a crafted hidden service
    descriptor.
    - debian/patches/CVE-2016-1254.patch: Fix parsing bug with unrecognized
      token at EOS.
    - CVE-2016-1254
  * SECURITY UPDATE: DoS (crash) via crafted data.
    - debian/patches/CVE-2016-8860.patch: Protect against NUL-terminated
      inputs.
    - CVE-2016-8860
  * SECURITY UPDATE: DoS (assertion failure and daemon exit) via a BEGIN_DIR
    rendezvous circuit.
    - debian/patches/CVE-2017-0376.patch: Fix assertion failure.
    - CVE-2017-0376
  * SECURITY UPDATE: Replay-cache protection mechanism is ineffective for v2
    onion services.
    - debian/patches/CVE-2017-8819.patch: Fix length of replaycache-checked
      data.
    - CVE-2017-8819
  * SECURITY UPDATE: DoS (application hang) via a crafted PEM input.
    - debian/patches/CVE-2017-8821.patch: Avoid asking for passphrase on
      junky PEM input.
    - CVE-2017-8821
  * SECURITY UPDATE: Relays, that have incompletely downloaded
    descriptors, can pick themselves in a circuit path, leading to a
    degradation of anonymity
    - debian/patches/CVE-2017-8822.patch: Use local descriptor object to
      exclude self in path selection.
    - CVE-2017-8822

 -- Eduardo Barretto <email address hidden>  Fri, 23 Nov 2018 14:25:06 -0200
Published in xenial-updates on 2018-11-22
Published in xenial-security on 2018-11-22
tor (0.2.9.14-1ubuntu1~16.04.3) xenial-security; urgency=medium

  * SECURITY UPDATE: Remote crash attack against directory authorities.
    - debian/patches/CVE-2018-0490.patch: Correctly handle NULL returns
      from parse_protocol_list when voting.
    - CVE-2018-0490

 -- Eduardo Barretto <email address hidden>  Thu, 22 Nov 2018 13:37:42 -0200
Superseded in disco-release on 2018-12-08
Deleted in disco-proposed on 2018-12-09 (Reason: moved to release)
tor (0.3.4.9-5) unstable; urgency=medium

  * New autopkgtest: setup-onion-service.

 -- Peter Palfrader <email address hidden>  Tue, 06 Nov 2018 16:08:35 +0100

Available diffs

Superseded in disco-release on 2018-11-10
Published in cosmic-release on 2018-07-14
Deleted in cosmic-proposed (Reason: moved to release)
tor (0.3.3.9-1) unstable; urgency=medium

  * New upstream version.

 -- Peter Palfrader <email address hidden>  Fri, 13 Jul 2018 22:24:19 +0200

Available diffs

Superseded in cosmic-release on 2018-07-14
Deleted in cosmic-proposed on 2018-07-15 (Reason: moved to release)
tor (0.3.3.8-1) unstable; urgency=medium

  * New upstream version.

 -- Peter Palfrader <email address hidden>  Tue, 10 Jul 2018 10:50:11 +0200

Available diffs

Superseded in cosmic-release on 2018-07-10
Deleted in cosmic-proposed on 2018-07-12 (Reason: moved to release)
tor (0.3.3.7-1) unstable; urgency=medium

  * New upstream version.

 -- Peter Palfrader <email address hidden>  Wed, 13 Jun 2018 09:31:15 +0200

Available diffs

Superseded in cosmic-release on 2018-06-14
Deleted in cosmic-proposed on 2018-06-15 (Reason: moved to release)
tor (0.3.3.6-1) unstable; urgency=medium

  * New upstream version, upload 0.3.3.x tree to unstable.
  * Start using upstream's minimal torrc as our default /etc/tor/torrc.
  * Put longer torrc.sample into /usr/share/doc.

 -- Peter Palfrader <email address hidden>  Wed, 23 May 2018 00:08:43 +0200

Available diffs

Superseded in cosmic-release on 2018-05-24
Published in bionic-release on 2018-03-20
Deleted in bionic-proposed (Reason: moved to release)
tor (0.3.2.10-1) unstable; urgency=medium

  * New upstream version.
    - Includes an important security fix for a remote crash attack against
      directory authorities.
      [TROVE-2018-001 and CVE-2018-0490]
    - Additionally, backports a fix for Tor#24700, which was originally
      fixed in 0.3.3.2-alpha but had its severity upgraded now as it can be
      remotely triggered and can crash relays.
      [TROVE-2018-002 and CVE-2018-0491]

 -- Peter Palfrader <email address hidden>  Sat, 03 Mar 2018 14:37:34 +0100
Published in artful-updates on 2018-03-01
Published in artful-security on 2018-03-01
tor (0.3.0.13-0ubuntu1~17.10.2) artful-security; urgency=medium

  * No change rebuild for the security pocket.

 -- Seth Arnold <email address hidden>  Wed, 28 Feb 2018 14:53:07 -0800
Superseded in xenial-updates on 2018-11-22
Superseded in xenial-security on 2018-11-22
tor (0.2.9.14-1ubuntu1~16.04.2) xenial-security; urgency=medium

  * No-change rebuild for the security pocket.

 -- Seth Arnold <email address hidden>  Wed, 28 Feb 2018 14:47:47 -0800
Superseded in artful-updates on 2018-03-01
Deleted in artful-proposed on 2018-03-02 (Reason: moved to -updates)
tor (0.3.0.13-0ubuntu1~17.10.1) artful; urgency=medium

  [ Peter Palfrader ]
  * Change "AppArmorProfile=system_tor" to AppArmorProfile=-system_tor,
    causing all errors while switching to the new apparmor profile to
    be ignored.  This is not ideal, but for now it's probably the
    best solution. Thanks to intrigeri; closes: #880490.

  [ Simon Deziel ]
  * New upstream version: 0.3.0.13 (LP: #1731698)
    - Fix a denial of service bug where an attacker could use a
      malformed directory object to cause a Tor instance to pause while
      OpenSSL would try to read a passphrase from the terminal. (Tor
      instances run without a terminal, which is the case for most Tor
      packages, are not impacted.) Fixes bug 24246; bugfix on every
      version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
      Found by OSS-Fuzz as testcase 6360145429790720.
    - Fix a denial of service issue where an attacker could crash a
      directory authority using a malformed router descriptor. Fixes bug
      24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
      and CVE-2017-8820.
    - When checking for replays in the INTRODUCE1 cell data for a
      (legacy) onion service, correctly detect replays in the RSA-
      encrypted part of the cell. We were previously checking for
      replays on the entire cell, but those can be circumvented due to
      the malleability of Tor's legacy hybrid encryption. This fix helps
      prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
      0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
      and CVE-2017-8819.
    - Fix a use-after-free error that could crash v2 Tor onion services
      when they failed to open circuits while expiring introduction
      points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
      also tracked as TROVE-2017-013 and CVE-2017-8823.
    - When running as a relay, make sure that we never build a path
      through ourselves, even in the case where we have somehow lost the
      version of our descriptor appearing in the consensus. Fixes part
      of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
      as TROVE-2017-012 and CVE-2017-8822.
    - When running as a relay, make sure that we never choose ourselves
      as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
      issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
  * New upstream version: 0.3.0.12
    - Directory authority changes
  * New upstream version: 0.3.0.11
    - Fix TROVE-2017-008: Stack disclosure in hidden services logs when
      SafeLogging disabled (CVE-2017-0380)
  * debian/rules: stop overriding micro-revision.i

Superseded in xenial-updates on 2018-03-01
Deleted in xenial-proposed on 2018-03-02 (Reason: moved to -updates)
tor (0.2.9.14-1ubuntu1~16.04.1) xenial; urgency=medium

  [ Peter Palfrader ]
  * apparmor: use Pix instead of PUx for obfs4proxy, giving us
    better confinement of the child process while actually working
    with systemd's NoNewPrivileges.  (closes: #867342)
  * Do not rely on aa-exec and aa-enabled being in /usr/sbin in the
    SysV init script.  This change enables apparmor confinement
    on some system-V systems again.  (closes: #869153)
  * Update apparmor profile: replace CAP_DAC_OVERRIDE with
    CAP_DAC_READ_SEARCH to match the systemd capability bounding set
    changed with 0.3.0.4-rc-1.  This change will allow tor to start
    again under apparmor if hidden services are configured.
    Patch by intrigeri.  (closes: #862993)
  * Replace CAP_DAC_OVERRIDE with CAP_DAC_READ_SEARCH in systemd's service
    capability bounding set.  Read access is sufficient for Tor (as root on
    startup) to check its onion service directories (see #847598).
  * Change "AppArmorProfile=system_tor" to AppArmorProfile=-system_tor,
    causing all errors while switching to the new apparmor profile to
    be ignored.  This is not ideal, but for now it's probably the
    best solution. Thanks to intrigeri; closes: #880490.

  [ Simon Deziel ]
  * Backport 0.2.9.14 to 16.04 (LP: #1731698)
  * debian/rules: stop overriding micro-revision.i
  * debian/control: drop build-conflicts
  * debian/control: Limit the seccomp build-dependency to [amd64 i386 x32 armel armhf]
  * Resync with Debian Stretch

Superseded in bionic-release on 2018-03-20
Deleted in bionic-proposed on 2018-03-22 (Reason: moved to release)
tor (0.3.2.9-1build1) bionic; urgency=high

  * No change rebuild against openssl1.1.

 -- Dimitri John Ledkov <email address hidden>  Mon, 05 Feb 2018 23:29:18 +0000
Superseded in bionic-release on 2018-02-08
Deleted in bionic-proposed on 2018-02-10 (Reason: moved to release)
tor (0.3.2.9-1) unstable; urgency=medium

  * New upstream version, upload 0.3.2.x tree to unstable.

 -- Peter Palfrader <email address hidden>  Tue, 16 Jan 2018 10:49:46 +0100

Available diffs

Superseded in bionic-release on 2018-01-23
Deleted in bionic-proposed on 2018-01-25 (Reason: moved to release)
tor (0.3.1.9-1) unstable; urgency=high

  * New upstream version, including among others:
    - Fix a denial of service bug where an attacker could use a
      malformed directory object to cause a Tor instance to pause while
      OpenSSL would try to read a passphrase from the terminal. (Tor
      instances run without a terminal, which is the case for most Tor
      packages, are not impacted.) Fixes bug 24246; bugfix on every
      version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
      Found by OSS-Fuzz as testcase 6360145429790720.
    - Fix a denial of service issue where an attacker could crash a
      directory authority using a malformed router descriptor. Fixes bug
      24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
      and CVE-2017-8820.
    - When checking for replays in the INTRODUCE1 cell data for a
      (legacy) onion service, correctly detect replays in the RSA-
      encrypted part of the cell. We were previously checking for
      replays on the entire cell, but those can be circumvented due to
      the malleability of Tor's legacy hybrid encryption. This fix helps
      prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
      0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
      and CVE-2017-8819.
    - Fix a use-after-free error that could crash v2 Tor onion services
      when they failed to open circuits while expiring introduction
      points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
      also tracked as TROVE-2017-013 and CVE-2017-8823.
    - When running as a relay, make sure that we never build a path
      through ourselves, even in the case where we have somehow lost the
      version of our descriptor appearing in the consensus. Fixes part
      of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
      as TROVE-2017-012 and CVE-2017-8822.
    - When running as a relay, make sure that we never choose ourselves
      as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
      issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
  * Build-depend on libcap-dev on linux-any so we can build tor with
    capabilities support to retain the capability to bind to low ports;
    closes: #882281, #700179.

 -- Peter Palfrader <email address hidden>  Fri, 01 Dec 2017 23:32:58 +0100

Available diffs

Superseded in bionic-release on 2017-12-02
Deleted in bionic-proposed on 2017-12-04 (Reason: moved to release)
tor (0.3.1.8-2) unstable; urgency=medium

  * Recent linux packages in Debian have enabled the apparmor
    Linux-Security-Module by default.  Therefore, users are likely to have
    apparmor support not only built into their kernel but also actively
    enabled at runtime.  Unfortunately, without the apparmor package
    being installed, systemd's AppArmorProfile= service setting will
    cause the unit to fail to start.
    .
    Change "AppArmorProfile=system_tor" to AppArmorProfile=-system_tor,
    causing all errors while switching to the new apparmor profile to
    be ignored.  This is not ideal, but for now it's probably the
    best solution.
    .
    Thanks to intrigeri; closes: #880490.

 -- Peter Palfrader <email address hidden>  Thu, 02 Nov 2017 21:31:27 +0100
Superseded in bionic-proposed on 2017-11-03
tor (0.3.1.8-1) unstable; urgency=medium

  * New upstream version.

 -- Peter Palfrader <email address hidden>  Sun, 29 Oct 2017 19:58:03 +0100
Superseded in xenial-updates on 2018-02-21
Deleted in xenial-proposed on 2018-02-22 (Reason: moved to -updates)
tor (0.2.9.11-1ubuntu1~16.04.1) xenial; urgency=medium

  * Backport from Debian Stretch to Xenial. Ubuntu Delta: (LP: #1710753)
    - Limit the seccomp build-dependency to [amd64 i386 armhf].
    - Drop build-conflicts.
    - Update debian/micro-revision.i to match 0.2.9.11 commit ID.
    - Use DAC_READ_SEARCH instead of DAC_OVERRIDE for Apparmor and
      systemd units. Cherry picked from 0.3.0.10-1 and 0.3.0.4-rc-1.
    - Limit the seccomp build-dependency to [amd64 i386 x32 armel armhf].

 -- Simon Deziel <email address hidden>  Tue, 15 Aug 2017 02:57:56 +0000
Obsolete in zesty-updates on 2018-06-22
Deleted in zesty-proposed on 2018-06-22 (Reason: moved to -updates)
tor (0.2.9.11-1ubuntu1) zesty; urgency=medium

  * Backport from Debian Stretch to Zesty. Ubuntu Delta: (LP: #1710753)
    - Limit the seccomp build-dependency to [amd64 i386 armhf].
    - Drop build-conflicts.
    - Update debian/micro-revision.i to match 0.2.9.11 commit ID.
    - Use DAC_READ_SEARCH instead of DAC_OVERRIDE for Apparmor and
      systemd units. Cherry picked from 0.3.0.10-1 and 0.3.0.4-rc-1.

 -- Simon Deziel <email address hidden>  Tue, 15 Aug 2017 02:57:56 +0000
Superseded in bionic-release on 2017-11-03
Published in artful-release on 2017-08-13
Deleted in artful-proposed (Reason: moved to release)
tor (0.3.0.10-1) unstable; urgency=medium

  * New upstream version.
  * Update apparmor profile: replace CAP_DAC_OVERRIDE with
    CAP_DAC_READ_SEARCH to match the systemd capability bounding set
    changed with 0.3.0.4-rc-1.  This change will allow tor to start
    again under apparmor if hidden services are configured.
    Patch by intrigeri.  (closes: #862993)
  * Remove tor-dbg binary package.  Nowadays Debian's toolchain
    automatically builds packages containing debugging symbols.  The new
    tor-dbgsym package will end up in the debian-debug archive.
    This tor-dbgsym package will Replace/Break tor-dbg versions
    prior to 0.3.1.5-alpha for now (to match the version in experimental
    with the same change), but as we keep providing backported builds for
    older suites, and since those keep the tor-dbg package for now,
    we'll likely keep increasing this version in future releases.
    (closes: #867547)
  * The dbgsym migration options require debhelper >= 9.20160114; update
    build dependency list accordingly.

 -- Peter Palfrader <email address hidden>  Sun, 13 Aug 2017 17:24:23 +0200
Superseded in artful-release on 2017-08-13
Deleted in artful-proposed on 2017-08-15 (Reason: moved to release)
tor (0.3.0.9-1build1) artful; urgency=medium

  * No-change rebuild against libevent-2.1-6

 -- Steve Langasek <email address hidden>  Mon, 31 Jul 2017 02:54:09 +0000
Superseded in artful-release on 2017-08-10
Deleted in artful-proposed on 2017-08-11 (Reason: moved to release)
tor (0.3.0.9-1) unstable; urgency=medium

  * New upstream version, upload 0.3.0.x tree to unstable.
    - Fixes TROVE-2017-006: Regression in guard family avoidance
      (closes: #866799; CVE-2017-0377).
  * Remove debian/README.{polipo,privoxy} as using them is not recommended.
    (Torbrowser is the better option for users browsing the web.)

 -- Peter Palfrader <email address hidden>  Sun, 02 Jul 2017 00:53:02 +0200

Available diffs

Superseded in artful-release on 2017-07-02
Deleted in artful-proposed on 2017-07-04 (Reason: moved to release)
tor (0.2.9.11-1) unstable; urgency=high

  * New upstream version.
    - Fix a remotely triggerable assertion failure caused by receiving a
      BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
      22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
      on 0.2.2.1-alpha.  (closes: #864424)

 -- Peter Palfrader <email address hidden>  Thu, 08 Jun 2017 18:48:46 +0200
Superseded in artful-release on 2017-06-09
Obsolete in zesty-release on 2018-06-22
Deleted in zesty-proposed on 2018-06-22 (Reason: moved to release)
tor (0.2.9.10-1ubuntu1) zesty; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Wed, 08 Mar 2017 08:25:29 +0100
Superseded in zesty-release on 2017-03-08
Deleted in zesty-proposed on 2017-03-09 (Reason: moved to release)
tor (0.2.9.9-1ubuntu1) zesty; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Wed, 01 Feb 2017 15:00:23 +0100
Superseded in zesty-release on 2017-02-01
Deleted in zesty-proposed on 2017-02-02 (Reason: moved to release)
tor (0.2.9.8-2ubuntu1) zesty; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Wed, 21 Dec 2016 10:56:27 +0100
Superseded in zesty-release on 2016-12-21
Deleted in zesty-proposed on 2016-12-22 (Reason: moved to release)
tor (0.2.8.11-2ubuntu1) zesty; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Sat, 10 Dec 2016 09:07:07 +0100
Superseded in zesty-release on 2016-12-10
Deleted in zesty-proposed on 2016-12-11 (Reason: moved to release)
tor (0.2.8.11-1ubuntu1) zesty; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Fri, 09 Dec 2016 23:41:39 +0100
Superseded in zesty-release on 2016-12-09
Deleted in zesty-proposed on 2016-12-11 (Reason: moved to release)
tor (0.2.8.10-1ubuntu1) zesty; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Mon, 05 Dec 2016 22:28:13 +0100
Superseded in zesty-release on 2016-12-06
Deleted in zesty-proposed on 2016-12-07 (Reason: moved to release)
tor (0.2.8.9-1ubuntu1) zesty; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Wed, 19 Oct 2016 11:39:41 +0200
Superseded in zesty-release on 2016-10-20
Obsolete in yakkety-release on 2018-01-23
Deleted in yakkety-proposed on 2018-01-23 (Reason: moved to release)
tor (0.2.8.8-1ubuntu1) yakkety; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Mon, 26 Sep 2016 09:02:25 +0200
Superseded in yakkety-release on 2016-09-26
Deleted in yakkety-proposed on 2016-09-27 (Reason: moved to release)
tor (0.2.8.7-1ubuntu1) yakkety; urgency=medium

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Thu, 25 Aug 2016 13:21:06 +0200
Superseded in yakkety-release on 2016-08-25
Deleted in yakkety-proposed on 2016-08-26 (Reason: moved to release)
tor (0.2.8.6-3ubuntu1) yakkety; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Tue, 23 Aug 2016 16:37:59 +0200
Superseded in yakkety-release on 2016-08-23
Deleted in yakkety-proposed on 2016-08-24 (Reason: moved to release)
tor (0.2.8.6-2ubuntu1) yakkety; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Sat, 13 Aug 2016 12:59:47 +0200
Superseded in yakkety-release on 2016-08-13
Deleted in yakkety-proposed on 2016-08-14 (Reason: moved to release)
tor (0.2.8.6-1ubuntu1) yakkety; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 armhf].

 -- Gianfranco Costamagna <email address hidden>  Thu, 04 Aug 2016 16:19:09 +0200
Superseded in yakkety-release on 2016-08-05
Deleted in yakkety-proposed on 2016-08-06 (Reason: moved to release)
tor (0.2.8.6-1) unstable; urgency=medium

  * New upstream version, upload 0.2.8.x tree to unstable.

 -- Peter Palfrader <email address hidden>  Tue, 02 Aug 2016 18:07:21 +0200
Superseded in yakkety-release on 2016-08-04
Published in xenial-release on 2016-03-22
Deleted in xenial-proposed (Reason: moved to release)
tor (0.2.7.6-1ubuntu1) xenial; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Limit the seccomp build-dependency to [amd64 i386 x32 armel armhf].

 -- Gianfranco Costamagna <email address hidden>  Tue, 22 Mar 2016 13:59:13 +0100
Superseded in xenial-release on 2016-03-22
Obsolete in wily-release on 2018-01-22
Deleted in wily-proposed on 2018-01-22 (Reason: moved to release)
tor (0.2.6.10-1ubuntu2) wily; urgency=medium

  * Limit the seccomp build-dependency to [amd64 i386 x32 armel armhf].
    Fails on other archs with
    error: 'mcontext_t {aka struct sigcontext}' has no member named 'M_SYSCALL'.

 -- Matthias Klose <email address hidden>  Mon, 05 Oct 2015 10:56:51 +0200
Superseded in wily-proposed on 2015-10-05
tor (0.2.6.10-1ubuntu1) wily; urgency=medium

  * Build using libseccomp on all architectures.

 -- Matthias Klose <email address hidden>  Sat, 03 Oct 2015 21:08:21 +0200
Superseded in trusty-updates on 2018-11-26
Superseded in trusty-security on 2018-11-26
tor (0.2.4.27-1build0.14.04.1) trusty-security; urgency=medium

  * Synced from Debian as a security update

Obsolete in vivid-updates on 2018-01-18
Obsolete in vivid-security on 2018-01-18
tor (0.2.5.12-1build0.15.04.1) vivid-security; urgency=medium

  * Sync from Debian as a security update

 -- Marc Deslauriers <email address hidden>  Wed, 29 Jul 2015 07:58:16 -0400
Superseded in wily-release on 2015-10-05
Deleted in wily-proposed on 2015-10-06 (Reason: moved to release)
tor (0.2.6.10-1) unstable; urgency=medium

  * New upstream version.

 -- Peter Palfrader <email address hidden>  Mon, 13 Jul 2015 18:05:34 +0200

Available diffs

Superseded in wily-release on 2015-07-14
Deleted in wily-proposed on 2015-07-15 (Reason: moved to release)
tor (0.2.6.9-1) unstable; urgency=medium

  * New upstream version.
  * Drop do-not-require-systemd and fix-sandbox-use-with-systemd.-bug-16212
    patches as they are included upstream now.

 -- Peter Palfrader <email address hidden>  Fri, 12 Jun 2015 22:01:42 +0200

Available diffs

Superseded in wily-release on 2015-06-15
Deleted in wily-proposed on 2015-06-16 (Reason: moved to release)
tor (0.2.6.8-5) unstable; urgency=medium

  * Sandboxing, when enabled, would prevent tor from working when
    started from systemd, as tor wasn't allowed to create a
    UNIX datagram socket.  Include that patch from upstream's git.

 -- Peter Palfrader <email address hidden>  Sat, 30 May 2015 16:44:27 +0200

Available diffs

Superseded in wily-release on 2015-05-31
Deleted in wily-proposed on 2015-06-01 (Reason: moved to release)
tor (0.2.6.8-4) unstable; urgency=medium

  * Remove whitespace around = in the systemd service file.  Apparently
    the spaces confuse deb-systemd-helper, which then resulted in Tor
    not being automatically started on boot (see #786418).
  * Remove obsolete After=syslog.target from systemd service file.

 -- Peter Palfrader <email address hidden>  Mon, 25 May 2015 22:02:39 +0200

Available diffs

Superseded in wily-release on 2015-05-26
Deleted in wily-proposed on 2015-05-27 (Reason: moved to release)
tor (0.2.6.8-3) unstable; urgency=low

  * debian/rules: Change order of --with commands to dh to ensure
    that we patch before calling autoreconf.

 -- Peter Palfrader <email address hidden>  Sun, 24 May 2015 08:58:18 +0200

Available diffs

Superseded in wily-release on 2015-05-24
Deleted in wily-proposed on 2015-05-25 (Reason: moved to release)
tor (0.2.6.8-2) unstable; urgency=low

  * debian/control: Depend on dh-systemd, libsystemd-dev, and pkg-config
    only on linux-any.
  * debian/rules: Build with systemd only if DEB_HOST_ARCH_OS is linux.
  * patch upstream's configure.ac to check for the existance of
    libsystemd rather than systemd.

 -- Peter Palfrader <email address hidden>  Sat, 23 May 2015 16:28:30 +0200

Available diffs

Superseded in wily-release on 2015-05-24
Deleted in wily-proposed on 2015-05-25 (Reason: moved to release)
tor (0.2.6.8-1) unstable; urgency=medium

  * New upstream version, upload 0.2.6.x tree to unstable.
  * Ship a systemd .service file (closes: #761403).
    Thanks to intrigeri and Arto Jantunen.
    - Build depend on dh-systemd, libsystemd-dev, pkg-config.
    - Build with --enable-systemd.
  * Autoreconf on build (closes: #783729).
    - Build depend on dh-autoreconf.

 -- Peter Palfrader <email address hidden>  Sat, 23 May 2015 09:57:44 +0200

Available diffs

Superseded in wily-release on 2015-05-23
Deleted in wily-proposed on 2015-05-25 (Reason: moved to release)
tor (0.2.5.12-1) unstable; urgency=medium


  * New upstream version, fixing hidden service related Denial of
    Service bugs:
    - Fix two remotely triggerable assertion failures (upstream bugs
      #15600 and #15601).
    - Disallow multiple INTRODUCE1 cells on the same circuit at introduction
      points, making overwhelming hidden services with introductions more
      expensive (upstream bug #15515).

 -- Peter Palfrader <email address hidden>  Mon, 06 Apr 2015 17:20:40 +0200

Available diffs

Superseded in wily-release on 2015-05-08
Obsolete in vivid-release on 2018-01-18
Deleted in vivid-proposed on 2018-01-19 (Reason: moved to release)
tor (0.2.5.10-1) unstable; urgency=medium


  * New upstream version.
  * Use "service tor reload", guarded by "service tor status" in logrotate
    instead as suggested by Dirk Griesbach (closes: #765407).

 -- Peter Palfrader <email address hidden>  Fri, 24 Oct 2014 16:05:28 +0200

Available diffs

Superseded in vivid-release on 2014-10-26
Obsolete in utopic-release on 2016-11-03
Deleted in utopic-proposed on 2016-11-03 (Reason: moved to release)
tor (0.2.4.23-1) unstable; urgency=medium


  * New upstream version.

 -- Peter Palfrader <email address hidden>  Mon, 28 Jul 2014 22:22:24 +0200

Available diffs

Superseded in utopic-release on 2014-07-29
Deleted in utopic-proposed on 2014-07-30 (Reason: moved to release)
tor (0.2.4.22-1) unstable; urgency=medium


  * New upstream version.

 -- Peter Palfrader <email address hidden>  Sat, 17 May 2014 09:59:02 +0200

Available diffs

Superseded in utopic-release on 2014-05-17
Deleted in utopic-proposed on 2014-05-19 (Reason: moved to release)
tor (0.2.4.21-1) unstable; urgency=low


  * New upstream version.

 -- Peter Palfrader <email address hidden>  Sat, 01 Mar 2014 19:35:30 +0100

Available diffs

Superseded in utopic-release on 2014-04-29
Published in trusty-release on 2013-12-27
Deleted in trusty-proposed (Reason: moved to release)
tor (0.2.4.20-1) unstable; urgency=low


  * New upstream version.
    - Avoid a crash bug when starting with a corrupted microdescriptor cache
      file. Fixes bug 10406; bugfix on 0.2.2.6-alpha (closes: #732105).
  * init script: make /var/log/tor if it does not exist anymore
    (closes: #732572).

 -- Peter Palfrader <email address hidden>  Wed, 25 Dec 2013 12:07:50 +0100

Available diffs

Superseded in trusty-release on 2013-12-27
Deleted in trusty-proposed on 2013-12-28 (Reason: moved to release)
tor (0.2.4.19-1) unstable; urgency=low


  * New upstream version.

 -- Peter Palfrader <email address hidden>  Thu, 12 Dec 2013 14:31:32 +0100

Available diffs

Superseded in trusty-release on 2013-12-14
Obsolete in saucy-release on 2015-04-24
Obsolete in raring-release on 2015-04-24
Deleted in raring-proposed on 2015-04-27 (Reason: moved to release)
tor (0.2.3.25-1) unstable; urgency=low


  * New upstream release.  The 0.2.3.x tree goes stable.
  * Dedicated to the memory of Len "rabbi" Sassaman (1980-2011).  We miss
    you, Len.

 -- Peter Palfrader <email address hidden>  Tue, 20 Nov 2012 22:00:34 +0100

Available diffs

Superseded in raring-release on 2012-11-21
Deleted in raring-proposed on 2012-11-22 (Reason: moved to release)
tor (0.2.3.24-rc-1) unstable; urgency=high


  * New upstream version:
    - Fix a group of remotely triggerable assertion failures related to
      incorrect link protocol negotiation. Found, diagnosed, and fixed
      by "some guy from France". Fix for CVE-2012-2250; bugfix on
      0.2.3.6-alpha.
    - Fix a denial of service attack by which any directory authority
      could crash all the others, or by which a single v2 directory
      authority could crash everybody downloading v2 directory
      information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
    - and more.

 -- Peter Palfrader <email address hidden>  Fri, 26 Oct 2012 09:15:09 +0200

Available diffs

Superseded in raring-release on 2012-10-29
Obsolete in quantal-release on 2015-04-24
tor (0.2.3.22-rc-1) unstable; urgency=high


  [ Peter Palfrader ]
  * New upstream version:
    - Fix an assertion failure in tor_timegm() that could be triggered
      by a badly formatted directory object. Bug found by fuzzing with
      Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.

  [ Stefano Zacchiroli ]
  * README.privoxy, README.polipo: explicitly set socks type to socks5.

 -- Peter Palfrader <email address hidden>  Tue, 11 Sep 2012 22:41:41 +0200

Available diffs

Superseded in quantal-release on 2012-09-18
tor (0.2.3.20-rc-1) unstable; urgency=low


  * New upstream version, including a couple security fixes:
    - Avoid read-from-freed-memory and double-free bugs that could occur
      when a DNS request fails while launching it. Fixes bug 6480.
    - Avoid an uninitialized memory read when reading a vote or consensus
      document that has an unrecognized flavor name. This read could
      lead to a remote crash bug. Fixes bug 6530.
    - Try to leak less information about what relays a client is
      choosing to a side-channel attacker.
  * Suggest the tor-arm controller.
  * Improve long descriptions with Roger's help.
  * Use https:// instead of git:// for the Vcs-Git URL.

 -- Peter Palfrader <email address hidden>  Tue, 07 Aug 2012 23:13:18 +0200

Available diffs

Superseded in quantal-release on 2012-08-08
tor (0.2.3.19-rc-1) unstable; urgency=low


  * New upstream version.

 -- Peter Palfrader <email address hidden>  Sat, 07 Jul 2012 12:15:49 +0200

Available diffs

Superseded in quantal-release on 2012-07-20
tor (0.2.3.18-rc-1) unstable; urgency=low


  * New upstream version.
  * Remove debian/patches/15_longer_test_timeout - something similar has been
    incorporated upstream (Re: Tor#6227).
  * Re-enable apparmor, if available:  Instead of confining /usr/sbin/tor by
    default, we now only confine the daemon that is launched from the init
    script.  We do this by calling aa-exec with the appropriate flags, if it
    is installed.  Therefore also suggest apparmor-utils.

 -- Peter Palfrader <email address hidden>  Fri, 29 Jun 2012 12:03:30 +0200

Available diffs

Superseded in quantal-release on 2012-07-01
tor (0.2.3.17-beta-3) unstable; urgency=low


  * Apply the correct SE-Linux label to /var/run/tor when creating the
    directory in the init script (closes: #678362).  Thanks to Russell Coker.
  * Hack up the unit tests to wait longer for the thread test to finish.
    This is not a real fix, but it will probably make it more likely that
    we successfully build on our mips/octeon machines (Re: Tor#6227).

 -- Peter Palfrader <email address hidden>  Sun, 24 Jun 2012 16:13:35 +0200
Superseded in quantal-release on 2012-06-29
tor (0.2.3.17-beta-2) unstable; urgency=low


  * Shipping and enabling the apparmor policy by default causes Tor to
    break for users who have apparmor enabled in enforcind mode and
    that, either in addition to or instead of running Tor as a system
    service (i.e. /etc/init.d/tor), also run Tor as their user or in
    some other means like launched from vidalia.  Therefore:
    .
    - No longer install apparmor policy by default.  It can be found in
      /usr/share/doc/tor if anybody is interested.
    - No longer build-depend on dh-apparmor, or suggest apparmor.
    - Also, clean up and remove old /etc/apparmor.d/usr.sbin.tor files
      on upgrade if they have not been changed by the user.
    .
    These changes relate to Debian Bug #670525 and fixes Tor ticket #6188.

 -- Peter Palfrader <email address hidden>  Mon, 18 Jun 2012 14:21:36 +0200
Superseded in quantal-release on 2012-06-19
tor (0.2.3.17-beta-1) unstable; urgency=low


  * New upstream version.
  * apparmor policy:
    - allow access to /var/log/tor/* and not just /var/log/tor/log*,
  * No longer create /var/run/tor in postint if it does not exist -
    the init script should take care of that.
  * Change the output of the init script to use lsb* functions:
    - Depend on lsb-base.
    - Makes the output pretty (closes: #676843)
  * Also, in the init script we are now less verbose, unless VERBOSE is
    set to yes in /etc/default/rcS (see the rcS(5) manual page):
    - pass --hush to tor on startup, so only warnings and errors are
      displayed, hiding any notice level log output,
    - do not report raising ulimit -n.

 -- Peter Palfrader <email address hidden>  Fri, 15 Jun 2012 15:26:38 +0200

Available diffs

Superseded in quantal-release on 2012-06-18
tor (0.2.2.37-1) unstable; urgency=medium


  * New upstream version, including:
    - Work around a bug in OpenSSL that broke renegotiation with TLS
      1.1 and TLS 1.2. Without this workaround, all attempts to speak
      the v2 Tor connection protocol when both sides were using OpenSSL
      1.0.1 would fail. Resolves ticket 6033.
    - When waiting for a client to renegotiate, don't allow it to add
      any bytes to the input buffer. This fixes a potential DoS issue.
      Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
    - and more.  See upstream's changelog.

 -- Peter Palfrader <email address hidden>  Tue, 12 Jun 2012 14:22:48 +0200

Available diffs

Superseded in quantal-release on 2012-06-13
tor (0.2.2.36-1) unstable; urgency=low


  * New upstream version, including updates to authority addresses, and
    a coulpe minor security issues, see upstream's changelog.

 -- Peter Palfrader <email address hidden>  Thu, 24 May 2012 11:08:24 +0200
Superseded in quantal-release on 2012-05-25
Published in precise-release on 2011-12-19
tor (0.2.2.35-1) unstable; urgency=high

  * New upstream version, fixing a heap overflow bug related to Tor's
    SOCKS code (CVE-2011-2778).
  * There no longer is a document called INSTALL to copy to
    usr/share/docs/tor, so get rid of the lintian override.  Since that was
    the only one in the tor package get rid of installing overrides for the
    tor package entirely - there's still one override in tor-geoipdb
    (closes Tor #4576).
 -- Ubuntu Archive Auto-Sync <email address hidden>   Mon,  19 Dec 2011 11:06:02 +0000

Available diffs

Superseded in precise-release on 2011-12-19
tor (0.2.2.34-1) unstable; urgency=high

  * New upstream version, fixing a couple of security relevant bugs
    such as guard enumeration (CVE-2011-2768) and bridge enumeration
    (CVE-2011-2769) issues.  For details consult the upstream changelog.
 -- Ubuntu Archive Auto-Sync <email address hidden>   Sun,  30 Oct 2011 10:30:20 +0000

Available diffs

Superseded in precise-release on 2011-10-30
tor (0.2.2.33-1) unstable; urgency=low

  * New upstream version.
  * Make patches/06_add_compile_time_defaults build without compiler warnings:
    - Correctly declare functions as having no arguments instead of not
      telling the compiler which arguments it'll have.
  * Suggest tor-arm (closes: #640265).
  * Downgrade socat and polipo|privoxy to Suggests (closes: #640264).

Available diffs

Superseded in precise-release on 2011-10-17
Obsolete in oneiric-release on 2015-04-24
tor (0.2.1.30-1build2) oneiric; urgency=low

  * No change rebuild against new libevent.
 -- Bhavani Shankar <email address hidden>   Sun, 10 Jul 2011 23:14:51 +0530
Superseded in oneiric-release on 2011-07-10
tor (0.2.1.30-1build1) oneiric; urgency=low

  * Rebuild for OpenSSL 1.0.0.
 -- Colin Watson <email address hidden>   Tue, 17 May 2011 11:55:54 +0100

Available diffs

Superseded in oneiric-release on 2011-05-17
Obsolete in natty-release on 2013-06-04
tor (0.2.1.30-1) unstable; urgency=low

  * New upstream version.
  * The tor specification files are no longer shipped in the tarball,
    so /usr/share/doc/tor/spec is no more.  They can be found online
    at <URL:https://gitweb.torproject.org/torspec.git/tree>.
 -- Krzysztof Klimonda <email address hidden>   Mon,  07 Mar 2011 14:44:59 +0000

Available diffs

175 of 107 results