[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

tor_0.2.1.21-1~bpo50+1_i386.changes is NEW



(new) tor-dbg_0.2.1.21-1~bpo50+1_i386.deb extra debug
debugging symbols for Tor
 This package provides the debugging symbols for Tor, The Onion Router.
 Those symbols allow your debugger to assign names to your backtraces, which
 makes it somewhat easier to interpret core dumps.
(new) tor-geoipdb_0.2.1.21-1~bpo50+1_all.deb extra comm
geoIP database for Tor
 This package provides a geoIP database for Tor, i.e. it maps IPv4 addresses
 to countries.
 .
 Bridges (special Tor relays that aren't listed in the main Tor directory) use
 this information to report which countries they get access from.  This allows
 the Tor network operators to learn if certain countries started blocking
 access to bridges.
(new) tor_0.2.1.21-1~bpo50+1.diff.gz optional comm
(new) tor_0.2.1.21-1~bpo50+1.dsc optional comm
(new) tor_0.2.1.21-1~bpo50+1_i386.deb optional comm
anonymizing overlay network for TCP
 Tor is a connection-based low-latency anonymous communication system which
 addresses many flaws in the original onion routing design.
 .
 In brief, Onion Routing is a connection-oriented anonymizing communication
 service. Users choose a source-routed path through a set of nodes, and
 negotiate a "virtual circuit" through the network, in which each node
 knows its predecessor and successor, but no others. Traffic flowing down
 the circuit is unwrapped by a symmetric key at each node, which reveals
 the downstream node.
 .
 Basically Tor provides a distributed network of servers ("onion
 routers"). Users bounce their tcp streams (web traffic, ftp, ssh, etc)
 around the routers, and recipients, observers, and even the routers
 themselves have difficulty tracking the source of the stream.
 .
 Note that Tor does no protocol cleaning.  That means there is a danger that
 application protocols and associated programs can be induced to reveal
 information about the initiator.  Tor depends on Privoxy and similar protocol
 cleaners to solve this problem.
 .
 Client applications can use the Tor network by connecting to the local
 onion proxy.  If the application itself does not come with socks support
 you can use a socks client such as tsocks.  Some web browsers like mozilla
 and web proxies like privoxy come with socks support, so you don't need an
 extra socks client if you want to use Tor with them.
 .
 This package enables only the onion proxy by default, but it can be configured
 as a relay (server) node.
 .
 Remember that this is development code -- don't rely on the current Tor
 network if you really need strong anonymity.
 .
 The latest information can be found at https://www.torproject.org/, or on the
 mailing lists, archived at http://archives.seul.org/or/talk/ or
 http://archives.seul.org/or/announce/.
(new) tor_0.2.1.21.orig.tar.gz optional comm
Changes: tor (0.2.1.21-1~bpo50+1) lenny-backports; urgency=low
 .
  * Build for bpo50.
  * Revert versioned Build-Depends on libssl-dev (>= 0.9.8k-6); add
    conflicts on libssl0.9.8 (>= 0.9.8k-6)
 .
tor (0.2.1.21-1) unstable; urgency=low
 .
  * New upstream version.
  * Drop patches/ce0a89e2-work-with-reneg-ssl.dpatch (already in
    upstream).
 .
tor (0.2.1.20-2) unstable; urgency=low
 .
  * Pick ce0a89e2624471272ffc4950c5069d9b81a7f0b9 from maint-0.2.1 git tree:
    - work with libssl that has renegotiation disabled by default.
    (debian/patches/ce0a89e2-work-with-reneg-ssl.dpatch)
  * Therefore build-depend on libssl-dev >= 0.9.8k-6.  If we build against
    earlier versions we will not work once libssl gets upgraded to a version
    that disabled renegotiations.
 .
tor (0.2.1.20-1) unstable; urgency=low
 .
  * New upstream version.
 .
tor (0.2.1.19-1) unstable; urgency=low
 .
  * New upstream version.
    - Make accessing hidden services on 0.2.1.x work right (closes: #538960).
    [More items are in the upstream changelog.]
 .
tor (0.2.1.18-1) unstable; urgency=low
 .
  * New upstream version.
 .
tor (0.2.1.17-rc-1) experimental; urgency=low
 .
  * New upstream version.
  * Update upstream URL in debian/copyright.
 .
tor (0.2.1.16-rc-1) experimental; urgency=low
 .
  * New upstream version.
  * No longer inform the user if/when we re-create the /var/run/tor
    directory in the init script.  With /var/run on tmpfs this is
    completely normal now so our message was just noise.
  * Stop shipping /var/run/tor in the package.
  * Only clean up permissions of /var/run/tor in postinst if the
    directory actually exists.
  * Update Standards-Version from 3.8.0 to 3.8.1.  No real changes
    required, we already support nocheck in DEB_BUILD_OPTIONS since
    August 2004, and we already create our var/run directory in the
    init script (tho we now no longer ship it either - see above).
  * Change debhelper compatibility version from 4 to 5:
    - Change dh_strip call from --dbg-package=tor
      to --dbg-package=tor-dbg.
    - Update versioned build time dependency on debhelper.
  * Forward port 06_add_compile_time_defaults.
 .
tor (0.2.1.15-rc-1) experimental; urgency=low
 .
  * New upstream version.
  * Change build time dependency on gs to ghostscript.
 .
tor (0.2.1.14-rc-1) experimental; urgency=low
 .
  * New upstream version.
  * Change Section of tor-dbg to debug.
 .
tor (0.2.1.13-alpha-1) experimental; urgency=low
 .
  * New upstream version.
 .
tor (0.2.1.12-alpha-1) experimental; urgency=low
 .
  * New upstream version, fixing several security relevant bugs:
     - Avoid a potential crash on exit nodes when processing malformed
       input.  Remote DoS opportunity (closes: #514579).
     - Fix a temporary DoS vulnerability that could be performed by
       a directory mirror (closes: #514580).
  * patches/06_add_compile_time_defaults: Only set the User option in
    the config if we run as root.  Do not set it when run as debian-tor
    as Tor then always insists on changing users which will fail.  (If
    we run as any other user we don't set our debian defaults anyway.)
 .
tor (0.2.1.11-alpha-1) experimental; urgency=high
 .
  * New upstream version:
    - Fixes a possible remote heap buffer overflow bug.
    - torify(1) manpage mentions DNS leaks now (closes: #495829).
  * README.Debian: No longer claim we change the default 'Group' setting
    when run as debian-user.  That setting no longer exists.
  * Forward port 03_tor_manpage_in_section_8.dpatch.
 .
tor (0.2.1.10-alpha-1) experimental; urgency=low
 .
  * New alpha release.
  * Forward port 03_tor_manpage_in_section_8.dpatch.
 .
tor (0.2.1.9-alpha-1) experimental; urgency=low
 .
  * New alpha release.
 .
tor (0.2.1.8-alpha-1) experimental; urgency=low
 .
  * New alpha release.
 .
tor (0.2.1.7-alpha-2) experimental; urgency=low
 .
  * No longer set now obsolete Group setting in built-in debian config.
 .
tor (0.2.1.7-alpha-1) experimental; urgency=low
 .
  * New alpha release.
 .
tor (0.2.1.6-alpha-1) experimental; urgency=low
 .
  * New alpha release.
  * Forward port 14_fix_geoip_warning.dpatch.
 .
tor (0.2.1.5-alpha-1) experimental; urgency=low
 .
  * New alpha release.
 .
tor (0.2.1.4-alpha-1) experimental; urgency=low
 .
  * New alpha release.
  * Do not build with openbsd's malloc unless enable-openbsd-malloc is in
    DEB_BUILD_OPTIONS.
 .
tor (0.2.1.2-alpha-1) experimental; urgency=low
 .
  * New alpha release.


Override entries for your package:

Announcing to backports-changes@lists.backports.org


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.

Reply to: