control 3.2 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374
  1. Source: tor
  2. Section: comm
  3. Priority: optional
  4. Maintainer: Peter Palfrader <weasel@debian.org>
  5. Build-Depends: debhelper (>= 5), libssl-dev, dpatch, zlib1g-dev, libevent-dev (>= 1.1), texlive-base-bin, texlive-latex-base, texlive-fonts-recommended, transfig, ghostscript, binutils (>= 2.14.90.0.7)
  6. Standards-Version: 3.8.1
  7. Homepage: https://www.torproject.org/
  8. Package: tor
  9. Architecture: any
  10. Depends: ${shlibs:Depends}, adduser, tsocks
  11. Conflicts: libssl0.9.8 (<< 0.9.8g-9)
  12. Recommends: privoxy | polipo (>= 1), socat, logrotate, tor-geoipdb
  13. Suggests: mixmaster, mixminion, anon-proxy
  14. Description: anonymizing overlay network for TCP
  15. Tor is a connection-based low-latency anonymous communication system which
  16. addresses many flaws in the original onion routing design.
  17. .
  18. In brief, Onion Routing is a connection-oriented anonymizing communication
  19. service. Users choose a source-routed path through a set of nodes, and
  20. negotiate a "virtual circuit" through the network, in which each node
  21. knows its predecessor and successor, but no others. Traffic flowing down
  22. the circuit is unwrapped by a symmetric key at each node, which reveals
  23. the downstream node.
  24. .
  25. Basically Tor provides a distributed network of servers ("onion
  26. routers"). Users bounce their tcp streams (web traffic, ftp, ssh, etc)
  27. around the routers, and recipients, observers, and even the routers
  28. themselves have difficulty tracking the source of the stream.
  29. .
  30. Note that Tor does no protocol cleaning. That means there is a danger that
  31. application protocols and associated programs can be induced to reveal
  32. information about the initiator. Tor depends on Privoxy and similar protocol
  33. cleaners to solve this problem.
  34. .
  35. Client applications can use the Tor network by connecting to the local
  36. onion proxy. If the application itself does not come with socks support
  37. you can use a socks client such as tsocks. Some web browsers like mozilla
  38. and web proxies like privoxy come with socks support, so you don't need an
  39. extra socks client if you want to use Tor with them.
  40. .
  41. This package enables only the onion proxy by default, but it can be configured
  42. as a relay (server) node.
  43. .
  44. Remember that this is development code -- don't rely on the current Tor
  45. network if you really need strong anonymity.
  46. .
  47. The latest information can be found at https://www.torproject.org/, or on the
  48. mailing lists, archived at http://archives.seul.org/or/talk/ or
  49. http://archives.seul.org/or/announce/.
  50. Package: tor-dbg
  51. Architecture: any
  52. Depends: tor (= ${binary:Version})
  53. Suggests: gdb
  54. Priority: extra
  55. Section: debug
  56. Description: debugging symbols for Tor
  57. This package provides the debugging symbols for Tor, The Onion Router.
  58. Those symbols allow your debugger to assign names to your backtraces, which
  59. makes it somewhat easier to interpret core dumps.
  60. Package: tor-geoipdb
  61. Architecture: all
  62. Priority: extra
  63. Depends: tor (>= ${source:Version})
  64. Description: geoIP database for Tor
  65. This package provides a geoIP database for Tor, i.e. it maps IPv4 addresses
  66. to countries.
  67. .
  68. Bridges (special Tor relays that aren't listed in the main Tor directory) use
  69. this information to report which countries they get access from. This allows
  70. the Tor network operators to learn if certain countries started blocking
  71. access to bridges.