Ubuntu

“tor” 0.2.0.31-1 source package in Ubuntu

Changelog

tor (0.2.0.31-1) unstable; urgency=low

  * New upstream version.
  * Tweak a few error messages in the init script to use the proper variables
    (not that it should matter, the Right One has the same value, but still)
    and to list more possible error reasons.

tor (0.2.0.30-2) unstable; urgency=low

  * Stop requiring that the binary in /usr/sbin/tor is still the same as the
    one that actually is the running tor when we try to stop or reload the
    daemon using the init script.  If the process is called tor, running as
    debian-tor, and the pid file agrees too then it probably is the Tor you
    want to stop (closes: #491246).

tor (0.2.0.30-1) unstable; urgency=low

  * New upstream version.

tor (0.2.0.29-rc-2) unstable; urgency=low

  * Upload to unstable.

tor (0.2.0.29-rc-1) experimental; urgency=low

  * New upstream version.
  * Warn the admin if the number of file descriptors on his system is
    tiny.

tor (0.2.0.28-rc-1) experimental; urgency=low

  * New upstream version.
  * Remove debian/patches/11_tor_as_root_more_helpful.dpatch as
    it is no longer needed:  We now setuid() to the Tor user
    when run as root and it all just works.
  * Add comments to the dpatch headers so lintian shuts up.
  * Add patches/14_fix_geoip_warning: Change geoipdb open failed message.
  * Require unit tests to pass again.

tor (0.2.0.27-rc-1) experimental; urgency=low

  * New upstream version.
  * Add tor-geoipdb arch: all package for the geoip database.
  * Update debian/rules so that there now is a binary-common target
    and the binary-indep and binary-arch targets call make with
    proper DH_OPTIONS options.  This is taken from the template
    that dh_make nowadays uses for multi-binary packages.
  * Unit tests are broken, yay.
  * Use ${binary:Version} to depend on the right tor binary package from
    the tor-dbg package instead of ${Source-Version}.  Some guy on the
    internet said the latter was deprecated.
  * Add Homepage: https://www.torproject.org/ field to control file.
  * And mention www.tp.o instead of the old tor.eff.org in the long
    description.
  * No longer ignore failure of make clean in the clean target.
  * Support passing of parallel=<n> in build options.
  * Change declared Standards-Version to 3.8.0.

tor (0.2.0.26-rc-1) experimental; urgency=critical

  * New upstream version.
  * Conflict with old libssls.
  * On upgrading from versions prior to, including, 0.1.2.19-2, or
    from versions later than 0.2.0 and prior to 0.2.0.26-rc do the
    following, and if we are a server (we have a /var/lib/tor/keys
    directory)
    - move /var/lib/tor/keys/secret_onion_key out of the way.
    - move /var/lib/tor/keys/secret_onion_key.old out of the way.
    - move /var/lib/tor/keys/secret_id_key out of the way if it was
      created on or after 2006-09-17, which is the day the bad
      libssl was uploaded to Debian unstable.
  * Add a NEWS file explaining this change.

tor (0.2.0.24-rc-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.23-rc-1) experimental; urgency=low

  * New upstream version.
  * Mention OpenBSD_malloc_Linux.c in debian/copyright.
  * Add a recommends on logrotate.

tor (0.2.0.22-rc-1) experimental; urgency=low

  * New upstream version.
  * Work around fig2dev failing to build the images on all archs
    (re #457568).
  * Build with --enable-openbsd-malloc, unless no-enable-openbsd-malloc is
    found in DEB_BUILD_OPTIONS.  Hopefully this deals with some of the
    horrible memory fragmentation that glibc's malloc causes.

tor (0.2.0.21-rc-1) experimental; urgency=low

  * New upstream version.
  * Run --verify-config before start/reload/restart as root.  No longer
    su - to debian-tor tor run it.  Given that we now even start Tor as
    root (it setuids later on) this should be fine (closes: #468566).

tor (0.2.0.20-rc-1) experimental; urgency=low

  * New upstream version.
  * Change the default for MAX_FILEDESCRIPTORS in our init script to depend
    on the number of system-wide available file descriptors:
    /proc/sys/fs/file-max is bigger than 80k, set ulimit -n to 32k, if it's
    greater than 40k set the limit to 16k, and when greater than 10k our limit
    shall be 8k descriptors.  If there are less than 20k FDs in the entire
    system default to a limit of only 1024.

    Big servers at the moment regularly use more than 10k FDs, so our old
    default of 8k no longer is sufficient.  On the other hand we don't want
    lower end systems to run out of FDs on Tor's account.
  * If we run as root also apply debian defaults.
  * Add User=debian-tor and Group=debian-tor to debian defaults.  That allows
    us to start Tor as root and have it setuid/setgid to the target user.
  * Change the init script to start Tor as root.  Now we should be able to
    bind to low port.

tor (0.2.0.19-alpha-1) experimental; urgency=low

  * New upstream version.
  * It's 2008.  Now is the time to add copyright statements for 2007.
  * Forward port 03_tor_manpage_in_section_8.dpatch.

tor (0.2.0.18-alpha-2) experimental; urgency=low

  * Work around fig2dev failing to build the images on mipsel like we do on
    sparc and s390 (re #457568)
  * Fix postinst find command that chowns stuff to the right user.  Find
    does weird things in the presence of !.

tor (0.2.0.18-alpha-1) experimental; urgency=low

  * New upstream version.
  * postinst: Remove the check that requires the debian-tor user
    to have a uid between 100 and 999.  There is no good reason
    to require this.  If the local admin moves the system users/uid-space
    to some other range then they probably have a good reason for that.
  * postinst: change wording if debian-tor's homedir is wrong, do not
    print anything if it is ok.
  * postinst: We were only fixing the permissions of /var/{lib,run,log}/tor
    when we were not upgrading.  Unfortunately the check doesn't work all
    that well usually in cases where the package was removed (not purged)
    and then later re-installed again.  Now we ensure proper ownership
    and modes for all the directories and files below /var/{lib,run,log}/tor
    (the dirs themselves included) every time we run postinst.
  * postinst: if we reboot between unpacking and configuring on some smart
    systems this will mean that we just lost /var/run/tor - creating it
    in the maintainer script if it doesn't exist.
  * Create logfiles in logrotate so that they come into the world with the
    correct mode (o-r).

tor (0.2.0.17-alpha-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.15-alpha-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.14-alpha-1) experimental; urgency=low

  * New upstream version.
  * Remove 13_r12907-fix-unit-tests.dpatch (Fix unit tests from HEAD) again -
    it's included upstream.
  * Work around fig2dev failing to build the images on sparc like we do on
    s390.

tor (0.2.0.13-alpha-1) experimental; urgency=low

  * New upstream version.
  * Fix unit tests from HEAD (13_r12907-fix-unit-tests.dpatch).

tor (0.2.0.12-alpha-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.11-alpha-1) experimental; urgency=low

  * New upstream version.
  * remove 12_r12235_do_not_crash_when_myfamily_is_set again, it's
    now part of upstream.

tor (0.2.0.9-alpha-2) experimental; urgency=low

  * Do not separate required lsb facilities with commas in the
    init script (closes: #448001).
  * Add 12_r12235_do_not_crash_when_myfamily_is_set.dpatch,
    from trunk/head.

tor (0.2.0.9-alpha-1) experimental; urgency=low

  * New upstream version.
  * Only create pid dir if we are about to start Tor (Luca Capello,
    closes: #447508).

tor (0.2.0.8-alpha-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.7-alpha-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.6-alpha-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.5-alpha-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.4-alpha-1) experimental; urgency=high

  * New upstream version.

tor (0.2.0.3-alpha-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.2-alpha-1) experimental; urgency=low

  * New upstream version.

tor (0.2.0.1-alpha-1) experimental; urgency=low

  * New upstream version.
  * Forward port 06_add_compile_time_defaults.
  * teTeX is no more, long live TeX Live:
    - remove build depends on tetex-bin, tetex-extra,
    - add build depends on texlive-base-bin for dvips and bibtex,
      texlive-latex-base for latex, and texlive-fonts-recommended for fonts
      like ptmr7t.

 -- Matt LaPlante <email address hidden>   Fri,  10 Oct 2008 11:10:32 +0100

Upload details

Uploaded by:
Matt LaPlante on 2008-10-10
Uploaded to:
Intrepid
Original maintainer:
Peter Palfrader
Component:
universe
Architectures:
any
Section:
comm
Urgency:
Critically Urgent

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size MD5 Checksum
tor_0.2.0.31.orig.tar.gz 2.1 MiB f3ab7d982ed295e7b25981c3910d5c2c
tor_0.2.0.31-1.diff.gz 76.1 KiB f57a530a9d6ffe27cbcbf8afd6a875bf
tor_0.2.0.31-1.dsc 1.1 KiB 649a24b65aab6b1fd76f5b2da5c6eec7

Available diffs

Binary packages built by this source

tor: 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 http://tor.eff.org/, or on the
 mailing lists, archived at http://archives.seul.org/or/talk/ or
 http://archives.seul.org/or/announce/.

tor-dbg: No summary available for tor-dbg in ubuntu jaunty.

No description available for tor-dbg in ubuntu jaunty.

tor-geoipdb: No summary available for tor-geoipdb in ubuntu intrepid.

No description available for tor-geoipdb in ubuntu intrepid.