Package: tor Version: 0.4.9.14-1~jammy+1 Architecture: amd64 Maintainer: Peter Palfrader Installed-Size: 5631 Depends: libc6 (>= 2.34), libcap2 (>= 1:2.10), libevent-2.1-7 (>= 2.1.8-stable), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 0.0.0~20120605), libssl3 (>= 3.0.0~~alpha1), libsystemd0, libzstd1 (>= 1.4.0), zlib1g (>= 1:1.1.4), adduser, lsb-base Recommends: logrotate, tor-geoipdb, torsocks Suggests: mixmaster, torbrowser-launcher, socat, apparmor-utils, nyx, obfs4proxy Conflicts: libssl0.9.8 (<< 0.9.8g-9) Homepage: https://www.torproject.org/ Priority: optional Section: net Filename: pool/main/t/tor/tor_0.4.9.14-1~jammy+1_amd64.deb Size: 1820336 SHA256: 1c77a669f6188c6241a4a9ea0ff96973475c4461e1ef154cf03795d33f4d8842 SHA1: 3eb5d9a42e9929e35928bdfa1791351bacb9d0a6 MD5sum: f6ec84deaef409bb74b004f0381af742 Description: anonymizing overlay network for TCP Tor is a connection-based low-latency anonymous communication system. . Clients choose a source-routed path through a set of relays, and negotiate a "virtual circuit" through the network, in which each relay knows its predecessor and successor, but no others. Traffic flowing down the circuit is decrypted at each relay, which reveals the downstream relay. . Basically, Tor provides a distributed network of relays. Users bounce their TCP streams (web traffic, ftp, ssh, etc) around the relays, and recipients, observers, and even the relays themselves have difficulty learning which users connected to which destinations. . This package enables only a Tor client by default, but it can also be configured as a relay and/or a hidden service easily. . Client applications can use the Tor network by connecting to the local socks proxy interface provided by your Tor instance. If the application itself does not come with socks support, you can use a socks client such as torsocks. . Note that Tor does no protocol cleaning on application traffic. There is a danger that application protocols and associated programs can be induced to reveal information about the user. Tor depends on Torbutton and similar protocol cleaners to solve this problem. For best protection when web surfing, the Tor Project recommends that you use the Tor Browser Bundle, a standalone tarball that includes static builds of Tor, Torbutton, and a modified Firefox that is patched to fix a variety of privacy bugs. Package: tor-geoipdb Source: tor Version: 0.4.9.14-1~jammy+1 Architecture: all Maintainer: Peter Palfrader Installed-Size: 25802 Depends: tor (>= 0.4.9.14-1~jammy+1) Breaks: tor (<< 0.2.4.8) Replaces: tor (<< 0.2.4.8) Homepage: https://www.torproject.org/ Priority: optional Section: net Filename: pool/main/t/tor/tor-geoipdb_0.4.9.14-1~jammy+1_all.deb Size: 2873314 SHA256: 838e0569fabbfcae389e78bf400eb6ce4f173ec4a86258d6cb8e12bec62d702b SHA1: 97e3700a6d544d0c3b26de98eb9e7a5243c8527f MD5sum: 397a06815088fda73009387c6b206492 Description: GeoIP database for Tor This package provides a GeoIP database for Tor, i.e. it maps IPv4 addresses to countries. . Bridge relays (special Tor relays that aren't listed in the main Tor directory) use this information to report which countries they see connections from. These statistics enable the Tor network operators to learn when certain countries start blocking access to bridges. . Clients can also use this to learn what country each relay is in, so Tor controllers like arm or Vidalia can use it, or if they want to configure path selection preferences.