Home Explore Help
Sign In
piros
/
tor
3
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 8182eb69cd
Branches Tags
tor
/
debian
/
control

control 2.6 KB
History Raw

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758 
  1. Source: tor
    2. 

  2. Section: comm
    3. 

  3. Priority: optional
    4. 

  4. Maintainer: Peter Palfrader <weasel@debian.org>
    5. 

  5. Build-Depends: debhelper (>= 4.1.65), libssl-dev, dpatch, zlib1g-dev, libevent-dev (>= 1.1), tetex-bin, tetex-extra, transfig, gs, binutils (>= 2.14.90.0.7)
    6. 

  6. Standards-Version: 3.6.2
    7. 

  7. 

  8. Package: tor
    9. 

  9. Architecture: any
    10. 

  10. Depends: ${shlibs:Depends}, adduser, tsocks
    11. 

  11. Recommends: privoxy, socat
    12. 

  12. Suggests: mixmaster, mixminion, anon-proxy
    13. 

  13. Description: anonymizing overlay network for TCP
    14. 

  14.  Tor is a connection-based low-latency anonymous communication system which
    15. 

  15.  addresses many flaws in the original onion routing design.
    16. 

  16.  .
    17. 

  17.  In brief, Onion Routing is a connection-oriented anonymizing communication
    18. 

  18.  service. Users choose a source-routed path through a set of nodes, and
    19. 

  19.  negotiate a "virtual circuit" through the network, in which each node
    20. 

  20.  knows its predecessor and successor, but no others. Traffic flowing down
    21. 

  21.  the circuit is unwrapped by a symmetric key at each node, which reveals
    22. 

  22.  the downstream node.
    23. 

  23.  .
    24. 

  24.  Basically Tor provides a distributed network of servers ("onion
    25. 

  25.  routers"). Users bounce their tcp streams (web traffic, ftp, ssh, etc)
    26. 

  26.  around the routers, and recipients, observers, and even the routers
    27. 

  27.  themselves have difficulty tracking the source of the stream.
    28. 

  28.  .
    29. 

  29.  Note that Tor does no protocol cleaning.  That means there is a danger that
    30. 

  30.  application protocols and associated programs can be induced to reveal
    31. 

  31.  information about the initiator.  Tor depends on Privoxy and similar protocol
    32. 

  32.  cleaners to solve this problem.
    33. 

  33.  .
    34. 

  34.  Client applications can use the Tor network by connecting to the local
    35. 

  35.  onion proxy.  If the application itself does not come with socks support
    36. 

  36.  you can use a socks client such as tsocks.  Some web browsers like mozilla
    37. 

  37.  and web proxies like privoxy come with socks support, so you don't need an
    38. 

  38.  extra socks client if you want to use Tor with them.
    39. 

  39.  .
    40. 

  40.  This package enables only the onion proxy by default, but it can be configured
    41. 

  41.  as a relay (server) node.
    42. 

  42.  .
    43. 

  43.  Remember that this is development code -- don't rely on the current Tor
    44. 

  44.  network if you really need strong anonymity.
    45. 

  45.  .
    46. 

  46.  The latest information can be found at http://tor.eff.org/, or on the
    47. 

  47.  mailing lists, archived at http://archives.seul.org/or/talk/ or
    48. 

  48.  http://archives.seul.org/or/announce/.
    49. 

  49. 

  50. Package: tor-dbg
    51. 

  51. Architecture: any
    52. 

  52. Depends: tor (= ${Source-Version})
    53. 

  53. Suggests: gdb
    54. 

  54. Priority: extra
    55. 

  55. Description: debugging symbols for Tor
    56. 

  56.  This package provides the debugging symbols for Tor, The Onion Router.
    57. 

  57.  Those symbols allow your debugger to assign names to your backtraces, which
    58. 

  58.  makes it somewhat easier to interpret core dumps.
    59.