Package: tor-dbgsym Architecture: i386 Version: 0.4.9.15-1vanir1~bpo11+1 Auto-Built-Package: debug-symbols Priority: optional Section: debug Source: tor Maintainer: Peter Palfrader Installed-Size: 5131 Depends: tor (= 0.4.9.15-1vanir1~bpo11+1) Breaks: tor-dbg (<< 0.3.1.5-alpha) Replaces: tor-dbg (<< 0.3.1.5-alpha) Filename: bullseye/tor-dbgsym_0.4.9.15-1vanir1~bpo11+1_i386.deb Size: 4762956 SHA256: 49f69e93969233a62c74b52a40daaf7c91dc7ae8cc12523ca9dadc51c8ce109b SHA512: d0a2bbfcccf4bfbca2fad25a386ae2a28bca799b7a5332d4a72f57d7f8952bbb6b51acad5695c3a5fdeafec77185a68f00c7d3dadd29e3203077b4034f671a4b Description: debug symbols for tor Build-Ids: 334e071c72379c28b84efb6a564c1b4a7bd53ca7 6bf3d33c17f180ae70084df3c55e2b922cf0f968 beed9a28c32a2bf80e6d4f12703ea245b43f08fc fa5a14ca19008ed5d39187db86a127477006bb10 Package: tor-dbgsym Architecture: amd64 Version: 0.4.9.16-1vanir1~bpo11+1 Auto-Built-Package: debug-symbols Priority: optional Section: debug Source: tor Maintainer: Peter Palfrader Installed-Size: 6284 Depends: tor (= 0.4.9.16-1vanir1~bpo11+1) Breaks: tor-dbg (<< 0.3.1.5-alpha) Replaces: tor-dbg (<< 0.3.1.5-alpha) Filename: bullseye/tor-dbgsym_0.4.9.16-1vanir1~bpo11+1_amd64.deb Size: 5836128 SHA256: d20a7437ce732e1fa31204e36e0e8e107b6e30f0863243041fdf43ac51633f5a SHA512: 4e6563dfbb3b7ff93a3c66977e191a0d33c8423585d8822f8a963dabe848da81f2d0ab929606230bcd8efdf943b6a5ba035d217d8495c6586a51c8485db9f292 Description: debug symbols for tor Build-Ids: 3cdb7742696fd33eb85eb4b3e24071a189056d22 5fc27c688036b18ae03df397ead3bea9a4d3c2ce 878d3b689d6ad8048cefef4b6bc6868353dbc4b6 962bd2951581101a8ba455a85f717fa1db8f1e41 Package: tor-geoipdb Architecture: all Version: 0.4.9.16-1vanir1~bpo11+1 Priority: optional Section: net Source: tor Maintainer: Peter Palfrader Installed-Size: 25917 Depends: tor (>= 0.4.9.16-1vanir1~bpo11+1) Breaks: tor (<< 0.2.4.8) Replaces: tor (<< 0.2.4.8) Filename: bullseye/tor-geoipdb_0.4.9.16-1vanir1~bpo11+1_all.deb Size: 2872064 SHA256: daeb562e3295f98eb9e3d498f7c281f6a51f9115ec16f2786f68c4ac813db614 SHA512: 9196ab57b357375244449e8fa6b8ae80f7776876529762e331077f631f5b5581e5c3204b6ef57bc0ea878e2ad0384186318939d70e48f8276e7967b29703a0d9 Homepage: https://www.torproject.org/ 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. Package: tor Architecture: i386 Version: 0.4.9.15-1vanir1~bpo11+1 Priority: optional Section: net Maintainer: Peter Palfrader Installed-Size: 6423 Depends: libc6 (>= 2.29), libcap2 (>= 1:2.10), libevent-2.1-7 (>= 2.1.8-stable), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 0.0.0~20120605), libssl1.1 (>= 1.1.1), 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) Filename: bullseye/tor_0.4.9.15-1vanir1~bpo11+1_i386.deb Size: 2214912 SHA256: 21e4fc03298c7bcc80a63844d196f3ec98a20144ae0a2b4d03657e8a14705d7b SHA512: 28a62eb6baa53ef2989d801df5d2e0e4f1dcadcfa4fe160a7997aaa0e3bd66d5d1aa493fcaaf18b2b1902884892110864735338db3b578de88f5948e7c19e941 Homepage: https://www.torproject.org/ 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 Architecture: amd64 Version: 0.4.9.16-1vanir1~bpo11+1 Priority: optional Section: net Maintainer: Peter Palfrader Installed-Size: 5910 Depends: libc6 (>= 2.29), libcap2 (>= 1:2.10), libevent-2.1-7 (>= 2.1.8-stable), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 0.0.0~20120605), libssl1.1 (>= 1.1.1), 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) Filename: bullseye/tor_0.4.9.16-1vanir1~bpo11+1_amd64.deb Size: 2140072 SHA256: a2ee2da547448b5463d38ddd1bdfbc79353cbe48e0535a0ec4ad124fccd90255 SHA512: cce42fb50e49a36bc77fb9c6fabece8636ce1a4416f524d2222eaf6f628420e842dcc851632eb61a23bda8ddb0e4283238143a7d23dbe3fad88eda99bd46b75a Homepage: https://www.torproject.org/ 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: toripscanner Architecture: all Version: 0.0~git20210815.f0365bd-0vanir1~bpo11+1 Priority: optional Section: utils Maintainer: Unit 193 Installed-Size: 116 Depends: python3-socks, python3-stem, python3-yaml, python3:any, tor Filename: bullseye/toripscanner_0.0~git20210815.f0365bd-0vanir1~bpo11+1_all.deb Size: 23892 SHA256: 9053f48b78a608b7a34077e61d4a5bae305a17574d864e9e0cb701a70ce17924 SHA512: 62686db1efd291fb8c2d9e6e4d0cb604023b89287d39f1b29eacf81fcbc4abd8e6e05a8e8075ef838d20a96d9fb30fdc3f7695786d00a3060ce3dae77afbeae6 Homepage: https://github.com/oftc/toripscanner Description: Scan Tor exits for the IPs they use There are many projects out there that produce a list of Tor exit IPs, but this one is the best. For us. Definitely. This is useful. . This scanner is better than all the all the rest because it does everything to find as many IPs exits may use as possible: . * It records ORPort IPs (both v4 and v6) from the server descriptors of all relays that can exit to OFTC infrastructure, regardless of whether or not they have the Exit flag. . * Through the relays that can connect to OFTC's user-facing ircds, we build circuits and connect to an ircd in order to get it to report to us what hostname/IP we are coming from. If we get a hostname, we lookup its A and AAAA records. . * For all relays that can connect to OFTC infrastructure, we see if the IPs in their descriptors have rDNS entries, and if so, we lookup A and AAAA records. . To be explicit: "OFTC infrastructure" includes our user-facing ircds and our web irc client. For relays that can only exit to our web IRC client, we only check their descriptors and do DNS queries.