- tor-relays - lists.torproject.org

Hardware specs for a high-bandwidth Tor exit?
by Christian Pietsch 09 Jul '20

09 Jul '20

Dear Tor friends, the NGO I am volunteering for (Digitalcourage e.V.) has been running modest Tor exits for many years. Now we finally have the opportunity to run a high-bandwidth exit relay because we found a data center with a nice internet connection (20 Gbit/s) we may use. My question is: What kind of hardware should we buy to utilize this bandwith? I am told that we need an SFP+ networking card to connect to the fibre optics cable, but what CPU and mainboard would you recommend nowadays? It should fit into a 1 height unit 19" enclosure. If you prefer to tell me in person: I will attend the Tor meetup in Brussels on Friday <https://blog.torproject.org/events/tor-meetup-brussels> and the subsequent Freedom Not Fear event <https://www.freedomnotfear.org/>. Cheers, Christian -- Christian Pietsch | volunteering for Digitalcourage e.V., Germany Digitalcourage e.V.: https://digitalcourage.de/ BigBrotherAwards Germany: https://bigbrotherawards.de/ Betting living without Google: https://pad.foebud.org/google-alternatives

3 3

Work with ISPs
by Charly Ghislain 09 Jul '20

09 Jul '20

Hi list, With the recent warning by nusenu about the malicious relays and the proposal to work around the issue , ive been wondering: Did anyone ever try to convince some isp to put a low-cap tor relay on the router of their 'unlimited bandwidth' clients? Or has there been any discussion on that matter already? I understand most would be strongly reticent, but I think some may find a commercial/marketing value in this. Thanks, Charly

2 1

Authority Nodes
by Vitor Milagres 06 Jul '20

06 Jul '20

Hi, I see the Authority Nodes are located only in North America and Europe. I would like to contribute to the TOR network as much as possible. I am currently running a node and I would like to make it an Authority Node as well. I am from Brazil and I believe it would possibly be a good idea to have a new Authority Node in South America. What are the requirements? What should I do to become one of them? FYI, the node I am running is 79DFB0E1D79D1306AF03A4B094C55A576989ABD1 Thanks, Vitor Milagres

8 9

Re: [tor-relays] >23% Tor exit relay capacity found to be malicious - call for support for proposal to limit large scale malicious actors
by niftybunny 06 Jul '20

06 Jul '20

How many of us do not have our own IP space and can already be verified by this? > On 5. Jul 2020, at 17:54, nusenu <nusenu-lists(a)riseup.net> wrote: > > Hi, > > I'm currently writing a follow-up blog post to [1] about a large scale malicious tor exit relay operator > that did run more than 23% of the Tor network's exit capacity (May 2020) before (some) of it got reported to the bad-relays team and > subsequently removed from the network by the Tor directory authorities. > After the initial removal the malicious actor quickly restored its activities and > was back at >20% of the Tor network's exit capacity within weeks (June 2020). > > [1] https://medium.com/@nusenu/the-growing-problem-of-malicious-relays-on-the-t… > > To prevent this from happening over and over again > I'm proposing two simple but to some extend effective relay requirements > to make malicious relay operations more expensive, time consuming, > less sustainable and more risky for such actors: > > a) require a verified email address for the exit or guard relay flag. > (automated verification, many relays) > > b) require a verified physical address for large operators (>=0.5% exit or guard probability) > (manual verification, low number of operators). > It is not required that the address is public or stored after it got verified. > For details see bellow [2]. > > 0.5% exit probability is currently about 500-600 Mbit/s of advertised bandwidth. > > > Q: How many operators would be affected by the physical address verification requirement if we use 0.5% as a threshold? > A: About 30 operators. > > There are currently about 18 exit [3] and 12 guard operators that run >0.5% exit/guard capacity > if we ignore the fresh exit groups from 2020. > Most exit operators (14 out of these 18) are organizations with public addresses or have their address published in WHOIS > anyway. > > At the end of the upcoming blog post I'd like to give people some idea as to how much support this proposal has. > > Please let me know if you find this idea to limit attackers useful, especially if you are a long term relay operator, > one of the 30 operators running >=0.5% exit/guard capacity, a Tor directory authority operator or part of The Torproject. > > > thanks for your support to fight malicious tor relays! > nusenu > -- > https://mastodon.social/@nusenu > > > [2] > Physical address verification procedure could look like this: > > The Torproject publishes a central registry of trusted entities that agreed to verify addresses of large scale operators. > > The registry is broken down by area so no central entity needs to see all addresses or is in the position to block all submissions. > (even though the number of physical address verifications are expected be stay bellow 50 for the time being). > > Examples could be: > > Riseup.net: US, ... > Chaos Computer Club (CCC) : DE, ... > DFRI: SE, ... > > (these organizations host Tor directory authorities) > > > - Relay operators that would like to run more than 0.5% guard/exit fraction select their respective area and contact the entity to > initiate verification. > > - before sending an address verification request the operator verifies that they meet the following requirements: > - the oldest relay is not younger than two months (https://community.torproject.org/relay/community-resources/swag/ ) > - all relays have a proper MyFamily configuration > - relays include the verified email address and PGP key fingerprint in the relay's ContactInfo > - at least one of their relays gained the exit or guard flag > - they have a sustained bandwidth usage of at least 100 Mbit/s (accumulated) > - intention to run the capacity for at least 4 months > > - upon receiving a request the above requirements are verified by the verification entity in addition to: > - relay(s) are currently running > - the address is in the entity's area > > - a random string is generated by the address verification entity and send with the welcome tshirt (if requested) to the operator > > - after sending the token the address is deleted > > - upon receiving the random string the operator sends it back via email to the verification entity > while signing the email with the PGP key mentioned in the relays ContactInfo > > - the verification entity compares the received string with the generated and mailed string > > - if the string matches the entity sends the relay fingerprint to the directory authority list to unlock the cap for the operator > > After this one-time procedure the operator can add more relays as long as they are in the same family as the approved relay (no new verification needed). > > > [3] > > exit operators running >=0.5% of exit probability > without exit groups from 2020 > (onionoo data as of 2020-07-03) > > abuse-contact(a)to-surf-and-protect.net 22.73 > Foundation for Applied Privacy 6.05 > John L. Ricketts, PhD <john AT quintex dot com> 5.6 > F3 Netze <abuse(a)f3netze.de> 5.47 > https://www.torservers.net 3.89 > Nicholas Merrill <nick AT calyx dot com> 2.48 > https://www.digitale-gesellschaft.ch/abuse/ 1.74 > Accessnow.org <abuse .AT. accessnow .DOT. org> 1.71 > Hart voor Internetvrijheid 1.63 > <zwiebeln at online de> 1.44 > TNinja <abuse-team at tor dot ninja> 1.43 > tech(a)emeraldonion.org 1.31 > Frenn vun der Enn FVDE 1 > https://www.artikel5ev.de/torcontact/ 0.74 > Nos oignons 0.71 > tor-abuse<at>mailbox<dot>org 0.67 > abuse-node49 AT posteo DOT de 0.57 > tor-operator(a)privateinternetaccess.com 0.52 > > 14 out of these 18 operators have their address already publicly listed because they are registered organizations or similar. > > >

1 0

Re: [tor-relays] >23% Tor exit relay capacity found to be malicious - call for support for proposal to limit large scale malicious actors
by Tor-Abuse 06 Jul '20

06 Jul '20

Hi nusenu, this sounds quite useful and I would like to support it. I would be fine to do an email and physical address verifiation. Cheers Fabian Am 05.07.20 um 17:54 schrieb nusenu: > nick AT calyx dot com

1 0

Tor is reporting my bridges as offline
by Eddie 03 Jul '20

03 Jul '20

Hi, I run 2 bridges on a hosted VPS. Tor is currently showing both these as offline for the last hour or so, but I can still connect to them from a Tor Browser and looking at the local logs, they are both running quite happily. Any ideas why they are showing as offline: https://metrics.torproject.org/rs.html#search/OhNoAnother Cheers.

3 4

Exit Relay throughput
by torix＠protonmail.com 20 Jun '20

20 Jun '20

Dear List, How important is the throughput on an exit relay? I realize that more is always better, making it harder to associate exit packets with input ones at the other end. My numbers: For the same price I can buy 2 exit relays that run about 3500 to 4000 connections or one that runs about 4300 to 4700 connections. The actual daily throughput varies a good deal, but the cheaper ones show about 15-20% less throughput, at around 330 GiB/day when I look at vnstat. Can I assume 2 is almost always better than one? Or is there a threshold below which packets are too easily tracked? I have no common sense about this. TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 2

"/var/tor/diff-cache" full!
by Salvatore Cuzzilla 19 Jun '20

19 Jun '20

Hi Folks, I'm running a non-exit relay (v0.4.2.7) on OpenBSD 6.7. The amount of files within "/var/tor/diff-cache" is steadily increasing. Up to almost 6G fulfilling the /var partition to the max. Is this an expected behavior? I there any solution to overcome it? ------- :wq, Salvatore.

5 5

directory servers working on updates?
by Paul Geurts 17 Jun '20

17 Jun '20

hi, anything up this weekend? [image: image.png] gr. Paul

2 2

ymkeo changing ISP coming Thursday
by René Ladan 15 Jun '20

15 Jun '20

Hi, I'm in the process of switching ISPs and if all goes well this should be complete by coming Thursday. So my relay (ymkeo, 4E8CE6F5651E7342C1E7E5ED031E82078134FB0D) will change its external IPv4 and IPv6 addresses. It is listed as a fallback directory mirror but currently not acting as one, so someone will have to update that list :) New IPv4: 185.238.129.9 /32 New IPv6: 2a10:3781:116:: /48 Regards, René

1 0

Consensus weight/Advertised bandwidth low on "Gigabit" ISP, despite ISP equipment upgrades
by Neel Chauhan 14 Jun '20

14 Jun '20

Hi tor-relays@, I run a FreeBSD-based Tor relay across two instances on "Wave G", a Gigabit ISP in the Seattle metro. You may also know them as CondoInternet or CascadeLink, but I joined only this year on a Wave-branded service. These relays have had low consensus weights since I got the service in January. The instances are below: * https://metrics.torproject.org/rs.html#details/8FABF4D266DF95216F6C646C6D6D… * https://metrics.torproject.org/rs.html#details/CE06BA1EA45FD32A79EAF7FE6A3B… My server and router are fine, I am in the single digits in terms of CPU use on both. The same exact server and router on Verizon FiOS in New York never gave me this issue. There was an underlying ISP performance issue impacting me which led consensus weight values to be low, but my ISP has since upgraded their equipment in my building. In general, my Internet performance has improved by magnitudes. However, my consensus weight has stayed more or less flat since the equipment upgrade, instead of jumping higher. What gives? How long would it usually take for the bandwidth scanners to measure the higher bandwidths? Should I re-key my relays and start from scratch? About switching ISPs, I'm not switching to Comcast for obvious well-documented reasons, and neither CenturyLink nor Frontier/Ziply Fiber serve me, not even copper. Best, Neel Chauhan === https://www.neelc.org/

2 1

IPv6 Port
by Josh Lawson 12 Jun '20

12 Jun '20

I currently have my IPv6 connection running on port 9001. From an anti-surveillance perspective, would I be better changing the port to 80? I have IPv4 running on 443. I appreciate it!

2 3

[NYX_NOTICE] Relay unresponsive -- how to troubleshoot?
by Davin Mertens 11 Jun '20

11 Jun '20

I keep getting NYX_NOTICEs about "Relay unresponsive". They happen every few hours, and last for minutes or sometimes a couple of hours before I get a "relay resumed" message. But, I don't see anything in the actual Tor logs to indicate that anything is wrong. Does anyone know how best to troubleshoot this? I *think* it's impacting my consensus weight and making it drop, and is keeping me from getting the Guard flag. This is the relay: https://metrics.torproject.org/rs.html#details/94626BD21119568EB301D1E7677B… Thanks for any tips!

3 3

Q: Is my bridge up?
by torix＠protonmail.com 11 Jun '20

11 Jun '20

I put up a new bridge and thought things were okay; I could see outbound, sometimes inbound connections in nyx, and seemed to have some throughput in the first nyx screen. The start up log lines seem okay: "Jun 10 11:05:07.000 [notice] Bootstrapped 100% (done): Done Jun 10 11:05:07.000 [notice] Now checking whether ORPort 108.52.155.127:11340 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Jun 10 11:05:09.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Jun 10 11:06:09.000 [notice] Performing bandwidth self-test...done. Jun 10 14:13:20.000 [notice] New control connection opened. Jun 10 15:33:16.000 [notice] No circuits are opened. Relaxed timeout for circuit 133 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. Jun 10 16:25:18.000 [notice] New control connection opened." And the 6hr heartbeat seems to show stuff is happening" "Jun 10 17:05:06.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 1.91 MB and received 5.84 MB." But when I use the bridge reach-ability test at https://bridges.torproject.org/scan/ It fails to find my obfs4 port. I have the two ports port-forwarded in my local router, but when I turn on ping to the router, nmap from outside sees them as filtered. Am I sending people down a black hole? Because tor does seem to be making tor connections. TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 3

Anyone getting Failed to find node for hop #2 of our path. Discarding this circuit. on relays after update?
by s7r 11 Jun '20

11 Jun '20

Hello, I have upgraded Tor to 0.4.5.0-alpha-dev-20200609T194914Z-1~d9.stretch+1 yesterday and got this message on all relays and bridges after upgrade: [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [notice] Our circuit 0 (id: 4) died due to an invalid selected path, purpose Testing circuit. This may be a torrc configuration issue, or a bug. [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. [warn] No available nodes when trying to choose node. Failing. [warn] Failed to find node for hop #2 of our path. Discarding this circuit. ... like 10-14 more times same message ... It eventually healed by itself on some relays, and on some only after another restart of the Tor process. I am only wondering if anyone else got this. What made me want to ask this is what I somehow got it on each and every relay and bridge I did the update on. Could this be triggered by a skewed clock? The virtual machines usually start with hwclock which is usually behind (virtualbox bug) and few seconds after boot ntp takes over and corrects the time. Will keep an eye on this. Things appear to run fine after it starts. Thanks.

1 0

Help via Skype teamviewer
by Pac-Man 11 Jun '20

11 Jun '20

I have everything ready to roll with a fresh Ubuntu install all updated could I get configuration help via Skype and teamviewer? Rgds, Pac-Man Sent from ProtonMail Mobile

3 2

Limiting Tor Resources
by AceOfSpadez79 10 Jun '20

10 Jun '20

When setting up a relay, we are told that Tor doesn't scale well beyond dual core systems. So with me having a 6 core CPU, is there a way to sandbox my relay and restrict system resources to say, at most 2 cores(4 threads) and 2 gigs of RAM? Now I know simply setting up a virtual machine could solve this, however I've had no luck getting the ORPort and DirPort to reach the outside world. Probably missed something in the Tor relay or KVM(hate virtualbox btw) documentation. \-AceOfSpadez79-

3 2

key expired and can't renew
by torix＠protonmail.com 09 Jun '20

09 Jun '20

Dear LIst, My bridge, tor version 0.4.2.7 stopped this morning with a bunch of lines like this: "It looks like I should try to generate and sign a new medium-term signing key, because the one I have is going to expire soon. To do that, I'm going to have to try to load the permanent master identity key. If the master identity key was not moved or encrypted with a passphrase, this will be done automatically and no further action is required. Otherwise, provide the necessary data using 'tor --keygen' to do it manually. [warn] We needed to load a secret key from /var/db/tor/keys/ed25519_master_id_secret_key, but i t was encrypted. Try 'tor --keygen' instead, so you can enter the passphrase." I put it up a month ago, so I assume this is the frst time the key needed to be changed. When I look at the keys directory, it looks the same as my still-running one, put ip 42 days ago. 42day one: /var/db/tor # ll keys total 28 -rw------- 1 _tor _tor 64 Apr 27 01:49 ed25519_master_id_public_key -rw------- 1 _tor _tor 96 Apr 27 01:49 ed25519_master_id_secret_key -rw------- 1 _tor _tor 172 May 26 02:00 ed25519_signing_cert -rw------- 1 _tor _tor 96 May 26 02:00 ed25519_signing_secret_key -rw------- 1 _tor _tor 888 Apr 27 01:49 secret_id_key -rw------- 1 _tor _tor 888 May 25 02:03 secret_onion_key -rw------- 1 _tor _tor 96 May 25 02:03 secret_onion_key_ntor Expired one: /var/log/tor # ll /var/db/tor/keys/ total 28 -rw------- 1 _tor _tor 64 May 9 01:29 ed25519_master_id_public_key -rw------- 1 _tor _tor 227 May 9 01:29 ed25519_master_id_secret_key_encrypted -rw------- 1 _tor _tor 172 May 9 01:29 ed25519_signing_cert -rw------- 1 _tor _tor 96 May 9 01:29 ed25519_signing_secret_key -rw------- 1 _tor _tor 888 May 9 02:09 secret_id_key -rw------- 1 _tor _tor 888 May 30 21:11 secret_onion_key -rw------- 1 _tor _tor 96 May 30 21:11 secret_onion_key_ntor I have never encrypted any tor keys; I just downloaded and installed it. Permissions seem the same on both. I can delete the keys directory and reinstall tor, but that's probably a hammer to kill a gnat. Hope that this has happened many times before and it's something simple. TIA, --Torix Sent with [ProtonMail](https://protonmail.com) Secure Email.

2 1

Tor end-of-life pre-removal notification for tor 0.4.1.x relays
by nusenu 08 Jun '20

08 Jun '20

Tor v0.4.1.x reached its end of life on 2020-05-20. https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… Tor developers are preparing a patch to remove 0.4.1 relays from the Tor network. If you are one of the affected tor relay operators (listed bellow), please upgrade to a supported tor release to protect yourself and the entire network from attacks exploiting older tor versions. List of end-of-life relays (updated daily): https://nusenu.github.io/OrNetStats/eolrelays It is recommended to configure your relays to auto-update to minimize the risk of outdated software. https://community.torproject.org/relay/setup/guard/ -- https://mastodon.social/@nusenu

1 0

Unused Relay - Why?
by petrarca＠protonmail.ch 07 Jun '20

07 Jun '20

Hello all, my relay is set up to support 42 Mbps, however does not get any real traffic routed through it (605EE4375EE4C38215C8949F5808863749FD4F4A). I checked anything I could think of but everything looks fine to me. Anyone with an idea what could be wrong here? Many thanks!

3 3

Nyx questions
by G 03 Jun '20

03 Jun '20

I have a few questions involving mostly the connection information provided by Nyx. In the past I have used standalone tor as a proxy for Firefox. At times Nyx would show my internal 127.x.x.x as the 'originating' IP and other times would show my internet facing 183.x.x.x as the originating IP. I now have two Ubuntu machines with older OS versions running Tor Browser 9.5. One machine has Nyx (-i 9151) showing the internal 127.x.x.x while the other shows 24.64.x.x as the originating IP. What is the significance of these differences? On a different topic are the torrc options the same for standalone tor and tor packaged with Tor Browser? For example with Tor Browser can additional socks ports be opened and utilized (obviously while Tor Browser is active)? Thanks (sorry if this info is documented somewhere - not easily found?)

1 0

Ubuntu Focal
by Pac-Man 01 Jun '20

01 Jun '20

When will there be support for Ubuntu 20.04 LTS? There does not seem to be a repo setup where you can use focal. I have plenty of bandwidth and everything to run a really good relay, but getting any kind of help is not happening. I have reached out to the TOR Project community and have received no answer. HOW do you expect new people to become a part of the TOR network when no one is there to answer any questions? Everything on youtube is old and outdated and no one seems to want to keep any software projects going. Maybe one day I will be good enough at this to help people in realtime, but until then unless there is anyone that is willing to help me I am going to probably mothball my relay. I am sad about it but life goes on. Other projects have needs as well. Rgds, Nicholas Miller Pacman Sent with [ProtonMail](https://protonmail.com) Secure Email.

4 3

Tor end-of-life pre-removal notification (tor 0.2.9.x, 0.4.0.x) - please upgrade
by nusenu 31 May '20

31 May '20

Tor developers are preparing the removal of outdated Tor relays from the network https://trac.torproject.org/projects/tor/ticket/32672 If you are one of the affected operators (listed bellow), please upgrade to a supported tor release to protect yourself and the entire network from attacks exploiting older tor versions. https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… The first 8 entries in the table bellow are in BCC of this email. +------------------------------------------------------------------------+-------------------+--------------------------+---------+ | contactInfo | versions | cwfr | #relays | +------------------------------------------------------------------------+-------------------+--------------------------+---------+ | thomaspli1(a)hotmail.com | 0.2.9.17 | 0.439104580848948 | 79 | | Gijs Rijnders (tor AT ip-eend DOT nl) | 0.4.0.5 | 0.3492794116027653 | 3 | | <ich[at]crashboy[dot]ws> | 0.2.9.16 | 0.14948582975193858 | 1 | | tor(a)govanify.com | 0.4.0.5 | 0.10492756264284253 | 1 | | stfn(a)hijnn.net | 0.4.0.5 | 0.09774074424058199 | 1 | | email: torchat(a)gmx.net | 0.4.0.6 | 0.09342864505015314 | 1 | | <Jannis> jannisde85(a)eclipso.eu | 0.4.0.5 | 0.08911655750125647 | 1 | | foorelay(a)hotmail.com | 0.2.9.17 | 0.08376956320717 | 10 | | help keep me running 1M2wWAB71wvaKwcGvBAGZin6PKKeYZVAcN stevecraft2@ya | 0.4.0.6 | 0.08049237076193094 | 1 | | KeFF NOC <noc AT keff dot org> | 0.4.0.5 | 0.08049237076193094 | 1 | | Tor Reactor <0d0[AT]protonmail.com> | u42omsvzmh7momdk.onion | BTC:13 | 0.4.0.5 | 0.07761764572933316 | 1 | | tor(a)moletrix.be | 0.4.0.5 | 0.07459917978849262 | 2 | | tor(a)texthtml.net | 0.4.0.5 | 0.0733055523596704 | 1 | | zwiebelring_LA(a)trashmail.com | 0.4.0.5 | 0.06899346481077373 | 1 | | tor4(a)example.org | 0.4.0.5 | 0.06728300072609272 | 4 | | JASON jasonenquiries(a)airmail.cc | 0.4.0.6 | 0.06381895509548485 | 1 | | 1Jwjq2AGPua8urdfZXtSbEQCKBQWF34qew ronstorabuse[a]protonmail-ch | 0.4.0.5 | 0.06324400892481208 | 1 | | abuse(a)maytownsend.is < abuse AT maytownsend dot is> | 0.4.0.5 | 0.06324400892481208 | 1 | | fredreic(at)tutanota(dot)com | 0.4.0.6 | 0.0626690627541393 | 1 | | jorge <spielman2(a)gmx.de> | 0.4.0.6 | 0.055338506354019046 | 1 | | Random Person <nobody AT example dot com> | 0.2.9.10,0.4.0.5 | 0.05462988518729617 | 4 | | tor-atomsk(a)protonmail.com | 0.4.0.5 | 0.05145762697793543 | 1 | | mail[at]nozel[.]org | 0.4.0.5 | 0.05030773172620684 | 2 | | william.santos(a)hotmail.co.uk | 0.4.0.5 | 0.04843916103709489 | 1 | | Theo Thomann - t_thomann1974(a)gmx.de | 0.4.0.5 | 0.04599564126692712 | 1 | | n0sign4l(a)n0sign4l.org | 0.2.9.16 | 0.04455827875062823 | 1 | | Dave Null <dave(a)null.net> | 0.2.9.17 | 0.043192781595280394 | 4 | | epstor (at) protonmail (dot) com | 0.4.0.6 | 0.0431209133239463 | 1 | | Network Operations <tor(a)t-3.net> | 0.4.0.2-alpha | 0.042114758980460465 | 1 | | torpids AT yahoo dot com - 1JYHfzVFVD7n2Sezz3DEHDFgGYjQWpDjqF | 0.4.0.5 | 0.04024618538096547 | 1 | | tor+torrot01(a)tzu.io | 0.4.0.5 | 0.03607783291954547 | 1 | | fak3(a)tuta.io | 0.4.0.5 | 0.03478420549072325 | 1 | | 4096R/5819E33F Zhongfu Li <tor at zhongfu dot li> | 0.4.0.5 | 0.034496732405386865 | 1 | | neyam(a)pm.me | 0.2.9.16 | 0.034496732405386865 | 1 | | ${CONTACT_GPG_FINGERPRINT} ${CONTACT_NAME} ${CONTACT_EMAIL} | 0.2.9.10 | 0.03305936697870493 | 1 | | phozon(a)protonmail.com | 0.4.0.5 | 0.0290347496047616 | 1 | | Ajour Redaktion - 0xB997262E6A382974 | 0.2.9.16 | 0.028747276519425213 | 1 | | tor atgoeshere nerdpol dotgoeshere org | 0.2.9.17 | 0.028747276519425213 | 1 | | OMP omp(a)cock.li | 0.2.9.16 | 0.02673496783245355 | 1 | | D9FE 4119 F082 6F15 93BD BD36 6162 DBA5 635E A16A Robin Raymond <FIRS | 0.2.9.16 | 0.026016283663921058 | 1 | | Anon g774i12a2(a)protonmail.com | 0.4.0.5 | 0.02539821798563935 | 2 | | FFFrelay1(a)protonmail.com | 0.2.9.16 | 0.024435186060145497 | 1 | | not-wanted [at] unknown [dot] com | 0.2.9.16 | 0.02242287591798231 | 1 | | tom(a)knep.me | 0.2.9.16 | 0.02156045666197315 | 1 | | Markus Peuhkuri <markus.peuhkuri(a)aalto.fi> | 0.2.9.16 | 0.020123092690482736 | 1 | | phenix | 0.2.9.16 | 0.020123092690482736 | 1 | | ruhtra.mar(a)gmail.com | 0.4.0.5 | 0.020123092690482736 | 1 | | tor(a)les.net | 0.2.9.10 | 0.019116938346996903 | 1 | | 4096R/34650013 La Quadrature du Net <tor(a)laquadrature.net> | 0.4.0.5 | 0.017392102745361626 | 1 | | me AT zandervdm.nl | 0.2.9.14 | 0.017248366202693433 | 1 | | tor.leak(a)spamgourmet.com | 0.4.0.5 | 0.017248366202693433 | 1 | | <tor AT b4ne dot de> | 0.4.0.5 | 0.016817156574688852 | 1 | | Admin <admin AT tor-relay dot io> | 0.4.0.5 | 0.016817156574688852 | 1 | | larka(a)nordberg.se | 0.2.9.16 | 0.015954738773871213 | 1 | | avdrelay(at)yopmail(dot)com [tor-relay.co] | 0.4.0.5 | 0.01581100223120302 | 1 | | Joe Rutkowski <joe plus tor ayt dreggle daht cahm> | 0.4.0.5 | 0.01581100223120302 | 1 | | tor-operator(a)eye.bz | 0.4.0.5 | 0.015092319517862052 | 1 | | christianbro <at> yandex <dot> ru - 1D1EjYEGHFPmc8RYXe5MmCqaZwqrXYaHgz | 0.2.9.14 | 0.014229901717044413 | 1 | | 0x0483E5F4 cyllos <contact AT cyllos dot me> | 0.4.0.5 | 0.012792537745554 | 1 | | tor_bob AT protonmail.com | 0.4.0.5 | 0.01236132811754942 | 1 | | Random Person <tor-trouble AT boldandbusted dot com> | 0.4.0.5 | 0.012102603068342432 | 1 | | dlv36(a)live.fr | 0.4.0.5 | 0.011642646859399974 | 1 | | Random Person sexyhexi(at)outlook(dot)at | 0.4.0.5 | 0.01149891031673178 | 1 | | soseksy(a)gmail.com | 0.2.9.16 | 0.011355173774063587 | 1 | | 0x1E7523CA911AC822 Markus Witt <markus.witt(a)rwth-aachen.de> | 0.2.9.16 | 0.01063649178831838 | 1 | | Boli 1GhfJRMcjb4jkk56EY3vAYo6RTD8V6c8e | 0.2.9.14 | 0.010492755973245949 | 1 | | jens <jens(a)chaox.net> - 11XxuJRkNp3CrxwP6DGdHwEa6UjZnpckp | 0.4.0.5 | 0.010492755973245949 | 1 | | 0x6F5BC20801248B85 pascal <pascal a t freifunk minus ibbenbueren dot n | 0.2.9.16 | 0.010377766739111394 | 1 | | https://hackeriet.no <comotion .AT. hackeriet .DOT. no> | 0.2.9.16 | 0.010349019430577755 | 1 | | hacksenkessel(a)gmail.com | 0.2.9.16 | 0.010205282887909561 | 1 | | ctci(a)fastimap.com | 0.4.0.5 | 0.010061546345241368 | 1 | | doof(a)doof.net | 0.2.9.16 | 0.009630337444832548 | 1 | | none | 0.2.9.17 | 0.009558469173498452 | 1 | | garadosgen2(a)protonmail.com | 0.4.0.5 | 0.009486600902164355 | 1 | | potlatch protonmail com | 0.4.0.5 | 0.009156007581623271 | 1 | | 0xFFFFFFFF Random Person <nobody AT example dot com> | 0.2.9.16,0.2.9.17 | 0.009049642812897218 | 2 | | LuxuryWood <luxurywood at safetymail.info> | 0.4.0.5 | 0.008624183101346716 | 1 | | John Marshall <johnmarshall AT seznam dot cz> | 0.2.9.14 | 0.00855231483001262 | 1 | | Dennis Emory Hannon / BackplaneDNS - abuse at BackplaneDNS(dot)org / x | 0.2.9.16 | 0.00832233636174351 | 1 | | info(a)egitmen.k12.tr | 0.2.9.17 | 0.008236094436142594 | 1 | | me(a)koshaq.net | 0.4.0.5 | 0.00790550111560151 | 1 | | tor at cybercyber dot wtf | 0.2.9.16 | 0.007833632844267413 | 1 | | rortor(a)rorvick.com | 0.4.0.5 | 0.0077761381817254005 | 3 | | torrelays A-T cyb3rwr3ck D-O-T net | 0.4.0.5 | 0.007761764572933316 | 1 | | AngelFreak <angelfreak(a)tsrv.pw> | 0.2.9.16 | 0.0071149508585222065 | 1 | | tilirim(a)gmail.com | 0.4.0.5 | 0.00702870893292129 | 1 | | Ivan <ivan(a)prokudin.org> | 0.4.0.5 | 0.006971214315854013 | 1 | | send@/dev/null | 0.2.9.16 | 0.006956840661587194 | 1 | | <aipfssubmit @ gmail . com> | 0.2.9.16 | 0.0069137196987867355 | 1 | | Nikita Borisov <tor-strudel-3f69fd(a)ssa.nikita.ca> | 0.2.9.14 | 0.0069137196987867355 | 1 | | tomkai IT Services <tor_relay AT tomkai dot ch> | 0.2.9.16 | 0.0062525323301088065 | 1 | | FlashTor at e.mail.de | 0.2.9.16 | 0.006137543459772132 | 2 | | atchoums(a)protonmail.com | 0.2.9.16 | 0.006008180571370758 | 1 | | hostmaster <hostmaster AT monomah dot link> | 0.2.9.16 | 0.005950686318101361 | 1 | | Aaron Kwei <aaronkwei(a)protonmail.ch> | 0.4.0.5 | 0.005893191701034084 | 1 | | zwiebelsaft(a)hotmail.com | 0.2.9.16 | 0.005691960541298613 | 1 | | falarcomleone | 0.2.9.16 | 0.005591345325228758 | 1 | | Tor Admin <tor -at- cs -dot- bu -dot- edu> | 0.2.9.17 | 0.005461982436827384 | 1 | | tor(a)different.name | 0.2.9.10,0.2.9.9 | 0.005408799870565417 | 2 | | Random Person <abl.spam AT gmail d0t com> | 0.4.0.5 | 0.0052176306780893356 | 1 | | Aleksandr Roldugin alexander(a)roldug.in | 0.2.9.17 | 0.005030773172620684 | 1 | | hardware [at] b3orion [dot] com | 0.2.9.17 | 0.005030773172620684 | 1 | | 1024D/F9CD0B8F Peter Buzanits <peter AT icb dot at> | 0.2.9.16 | 0.004887036993750371 | 1 | | adipembuddha ( at ) gmail ( dot ) com | 0.2.9.16 | 0.004887036993750371 | 1 | | Andrew Deason <adeason+tor AT dson dot org> | 0.4.0.5 | 0.004815168722416274 | 1 | | anonymous(a)ubuntu-tor-simply-setup.script.by.PeterDaveHello | 0.2.9.16 | 0.0047433004510821775 | 1 | | <dragonv1989v AT hotmail dot com> | 0.2.9.16 | 0.004599564272211865 | 1 | | <hellguard3(a)gmx.de> | 0.2.9.16 | 0.00447020138381049 | 1 | | Micah Sherr <msherr(a)cs.georgetown.edu> | 0.4.0.5 | 0.004427080421010032 | 1 | | tor(a)infincia.com | 0.4.0.5 | 0.004312091550673358 | 1 | | halloanjedendenichkenne(a)gmail.com | 0.4.0.5 | 0.00403899211960379 | 1 | | DuckSounds31(a)aol.com | 0.4.0.5 | 0.003938376721634995 | 2 | | 0xB5CC27E1 Paul Wouters <paul(a)nohats.ca> | 0.2.9.17 | 0.003880882286466658 | 1 | | Gorgothzilla tor(a)gorgothzilla.net | 0.2.9.16 | 0.003880882286466658 | 1 | | tor-operator(a)eadline.org | 0.2.9.17 | 0.003880882286466658 | 1 | | crackofdawn <AT> posteo (DOT) de | 0.2.9.16 | 0.0037371457437984645 | 1 | | tor -----symbol for email---- zigh in et to --separator-- org | 0.2.9.16 | 0.0037371457437984645 | 1 | | Scott Smith <tor AT scott-smith DOT us> | 0.2.9.16 | 0.003679651490529068 | 1 | | SerialBox <serialbox AT riseup DOT net> | 0.2.9.16 | 0.0035934095649281517 | 1 | | 211CA2D4/2281 885D DB14 376A 2882 BCDF C053 30B3 211C A2D4 Thomas <to | 0.4.0.5 | 0.003449673022259958 | 1 | | <johnyd adt firemail dooit cc> | 0.4.0.5 | 0.003449673022259958 | 1 | | Tom Ritter <tom(a)ritter.vg> | 0.4.0.5 | 0.003449673022259958 | 1 | | freenetwork AT protonmail dot com | 0.2.9.16 | 0.0032053212635219097 | 1 | | BobTheBuilder <jozefnagyjr(a)gmail.com> | 0.2.9.16 | 0.002860353924916126 | 1 | | <tor-op AT innolan dot net> | 0.4.0.5 | 0.0027884858354809694 | 1 | | Mr. Milk <mrmilk(a)xs4al.nl> | 0.2.9.16 | 0.0026734966013464145 | 1 | | set.element(a)gmail.com | 0.2.9.14 | 0.0025872548576444387 | 1 | | no_mail at no_mail dot null | 0.2.9.17 | 0.0025297602405771613 | 1 | | <tor(a)carnet.hr> | 0.2.9.16 | 0.0024435184968751855 | 1 | | 0xB8A168B3A02C01E3 <tor AT python273 dot pw> | 0.4.0.5 | 0.0023572765712742694 | 1 | | <OloTorRelay at gmail dot com> | 0.2.9.16 | 0.0022997821361059323 | 1 | | bund AT posteo dot de | 0.2.9.16 | 0.002199166556238197 | 1 | | admin(a)oniontip.com - 1HW9PqwzaHTTLgeZkBWdZ5Y7rTjqJS9Jmj | 0.2.9.16 | 0.0018685728718992323 | 1 | | steff <steffen dot jesus at googlemail dot com> | 0.2.9.16 | 0.0017535838196636178 | 1 | | J L jl02115+tor.watchtower2(a)gmail.com | 0.2.9.9 | 0.0017392101653967984 | 1 | | <ben + tor [at] graef . in> 128qLZCaGdoWhBTfaS7rytpbvG4mNTyAQm | 0.4.0.5 | 0.001724836511129979 | 1 | | busyspin <busyspin AT fastmail dot us> | 0.2.9.15 | 0.001724836511129979 | 1 | | Tormaster <tormaster AT no-fun.de> | 0.2.9.16 | 0.0016529684216948226 | 1 | | Chris Amin <tor(a)moonraptor.com> | 0.2.9.16 | 0.0015811001503607258 | 1 | | qeychon(a)gmail.com | 0.2.9.14 | 0.0015811001503607258 | 1 | | tor theatsign pwn party | 0.4.0.5 | 0.0015811001503607258 | 1 | | Random Person <e12firewall(a)gmail.com> | 0.2.9.16 | 0.0015667264960939065 | 1 | | Ruminant(at)freenet(dot)de [tor-relay.co] | 0.2.9.16 | 0.001552352841827087 | 1 | | 0x14294C3F Jonathan Frederickson <jonathan(a)terracrypt.net> | 0.2.9.14 | 0.0014948583157092799 | 1 | | cstdenis <cstdenis AT ctgameinfo dot com> | 0.4.0.5 | 0.001451737443858292 | 1 | | tor(a)fossencdi.org - 1EUdGyPZ2cgas4v4deWdDwnS97v1psawB5 | 0.2.9.16 | 0.0014373637895914726 | 1 | | ContactInfo Alexander Burger <abu(a)software-lab.de> | 0.2.9.16 | 0.0013942429177404847 | 1 | | DeinName popelmotzi(a)hotmail.de | 0.2.9.16 | 0.0013281241990625858 | 1 | | <count.zero.cdc(a)protonmail.ch> PGP FINGERPRINT: F767 8323 B141 4B91 D7 | 0.2.9.14 | 0.0012850032362621278 | 1 | | 1024D/0C667A3E Erik Andresen erik AT mailus dot de | 0.2.9.16 | 0.0012361329027044121 | 1 | | Tyler Cipriani <tyler AT tylercipriani dot com> | 0.2.9.16 | 0.0012016361324640457 | 1 | | pv(at)blueberry(dot)cz | 0.2.9.16 | 0.001195886716232053 | 2 | | crmh(a)posteo.de | 0.2.9.16 | 0.001195886670757318 | 1 | | 0xBF819544 Random Person <msc+tor ON cle.ar.it> | 0.2.9.14 | 0.0011642647223197855 | 1 | | Seshan Ravikumar <https://seshan.xyz or http://7snfudlzbmo35hxn.onion/ | 0.4.0.5 | 0.0011498910680529661 | 1 | | Random Person <mm266 AT 0box dot eu> | 0.4.0.5 | 0.0011355174137861468 | 1 | | Nohum <nohum dot oyzer AT gmail dot com> | 0.2.9.16 | 0.0011211437595193274 | 1 | | Random Person <kimpale AT keemail dot me> | 0.2.9.16 | 0.0010305898285878357 | 1 | | <admin AT bewilderbeest.net> | 0.2.9.17 | 0.001023403001454426 | 1 | | ibarz.jean(a)gmail.com | 0.2.9.16 | 0.001006154707283713 | 1 | | Krakow.pw <admin AT krakow dot pw> | 0.4.0.5 | 0.0009917810530168936 | 1 | | freitag381(a)gmail.com | 0.4.0.5 | 0.0009774073987500742 | 1 | | Random Admin <tor (AT) unpatented dot com> | 0.2.9.17 | 0.0009342864359496161 | 1 | | <debjit AT fastmail dot fm> | 0.2.9.16 | 0.0009242249234375777 | 2 | | Ben Wilhelm <zorba-tor-vaal(a)pavlovian.net> | 0.2.9.14 | 0.0008911655640986282 | 1 | | Someone at example dot com | 0.4.0.5 | 0.0008480446012981702 | 1 | | Damien Desfontaines <spam.tor-yatr(a)desfontain.es> (@TedOnPrivacy) | 0.2.9.16 | 0.0008250468454207294 | 1 | | mistralis (A)(T) protonmail _(c)&(o)$(m) | 0.2.9.16 | 0.0007287434527825098 | 1 | | ninja.turtle5(a)aol.com | 0.4.0.5 | 0.000704308286003652 | 1 | | Random Person <zhuknode45(a)lelik.org> | 0.2.9.16 | 0.0006468137144111097 | 1 | | Anagramix <anagramix AT protonmail dot com> | 0.2.9.16 | 0.0006180664513522061 | 1 | | t-1000(a)sigaint.org | 0.2.9.16 | 0.0005893191428185673 | 1 | | houmgabot <houmgabot AT protonmail dot com> | 0.2.9.16 | 0.0005677587068930734 | 1 | | 0xFFFFFFFF Random dude <testov123 AT gmail dot com> | 0.2.9.16 | 0.0005461982254928444 | 1 | | Esben Madsen <torberry-penguin [change this text to AT] minpingvin [po | 0.2.9.16 | 0.0005030773536418565 | 1 | | ENIGMA <enigmaunicamp AT tutanota dot com> | 0.4.0.5 | 0.0004455827820493141 | 1 | | tor-operator(a)throwaway.com | 0.4.0.5 | 0.00043120912778249476 | 1 | | muke101(a)protonmail.com | 0.2.9.16 | 0.00040677396100363694 | 1 | | Angry Tor <angrytor AT icloud dot com> | 0.2.9.10 | 0.00040246186472359113 | 1 | | RelayAdmin <toradmin.0mv(a)gishpuppy.com> | 0.2.9.14 | 0.00040246186472359113 | 1 | | Random Person <kalle.fester(a)outlook.com> | 0.2.9.16 | 0.00035934094739786815 | 1 | | Nym <tor.20.sokrat AT spamgourmet.com> 1JH2RueDoXvEaNEdQKByW3mj1C3HquW | 0.4.0.5 | 0.0003507167775751441 | 1 | | 0x57693E97FFF46F2D Alessandro Manfredi <a.n0on3-4t-gmail-d0t-com> | 0.2.9.16 | 0.0003305936843389645 | 1 | | apunkt at mailbox dot org | 0.2.9.15 | 0.00031622003007214516 | 1 | | <timon AT rtor dot nl> | 0.2.9.16 | 0.00030184639854269335 | 1 | | aze <aze AT anonsbh dot co> | 0.4.0.1-alpha-dev | 0.0002730991127464222 | 1 | | Ins0mnia Shells <orwell1984.info AT gmail dot com> | 0.4.0.5 | 0.00025872548121697037 | 1 | | The Onion <tor AT sommrey dot de> | 0.2.9.16 | 0.00024435184968751855 | 1 | | <tor AT jd dot nl> | 0.4.0.5 | 0.00022997821815806674 | 1 | | Random Person outofluck at gmail dot com | 0.2.9.16 | 0.00020123093236179557 | 1 | | <0x61455 delthis a%t protonmail dotcom> | 0.2.9.16 | 0.00018685728946365998 | 1 | | lyratorx at protonmail dot com | 0.4.0.5 | 0.00018398256997897988 | 1 | | djrodgerspryor+tor(a)gmail.com | 0.4.0.5 | 0.00017248365793420817 | 1 | | Scott Ramsay scottramsay45(a)gmail.com | 0.2.9.14 | 0.00017248365793420817 | 1 | | 4B73DCCA Autonomous Action <adm AT avtonom dot org> | 0.2.9.16 | 0.00015811001503607258 | 1 | | mark(a)encounterit.com.au | 0.4.0.5 | 0.00014373638350662077 | 1 | | 0x9CF49C5F Mkg20001 <mkg20001(a)gmail.com> | 0.2.9.14 | 0.0001408616526532569 | 1 | | freeInternet(a)whitehouse.gov | 0.4.0.5 | 0.0001408616526532569 | 1 | | tedsheep(a)protonmail.com | 0.2.9.16 | 0.00013942428722657496 | 1 | | 0x00aa5556 Hans-Christoph Steiner <root(a)guardianproject.info> | 0.2.9.16 | 0.0001365495563732111 | 1 | | 0x57F0D893 oz <oz AT cyprio dot net> | 0.2.9.16 | 0.0001365495563732111 | 1 | | johndoebravo(a)yandex.com | 0.4.0.5 | 0.0001264880097551213 | 2 | | Maurer01 <further(a)gmx.com> | 0.2.9.16 | 0.00012217592484375928 | 1 | | TOR contact <tor AT snabel punkt se> | 0.2.9.16 | 0.00012217592484375928 | 1 | | 0x49A5C7EB Martin 'The Bishop' Scheffler <bishop-tor(a)mondkalbantrieb.d | 0.2.9.16 | 0.0001121143782256695 | 1 | | Peter Tlusteck <tdipeter(a)hotmail.de> | 0.2.9.16 | 0.00010636491651894175 | 1 | | 2048R/AF1E829C | 0.2.9.16 | 0.00010205283160757972 | 1 | | Fractalia <fractalia (at) tutamail (dot) com> | 0.2.9.16 | 0.00009774073532753391 | 1 | | 4096R/CB09F22F Florian Lohoff <f(a)zz.de> | 0.4.0.5 | 0.00009630336990085198 | 1 | | Jabber.de Tornode Admin <tor AT jabber dot de> | 0.2.9.14 | 0.00009486601015851193 | 1 | | Marmal <marmal AT protonmail dot ch> | 0.2.9.16 | 0.00008911655413612607 | 1 | | me <tor(a)cool.ms> | 0.2.9.16 | 0.00007330555149565043 | 1 | | Piotr Maslanka <piotr dot maslanka at henrietta dot com dot pl> | 0.2.9.16 | 0.00006755610115760646 | 1 | | arianto.nugroho(a)gmail.com | 0.2.9.16 | 0.00006468137030424259 | 1 | | Aaron Bugher <aabugher(a)gmail.com> | 0.2.9.16 | 0.00006324400487756066 | 1 | | sentinel(a)storagedemon.net - 1GKkzW4enyL29QJEq3C7MSfvS1x9Bb1s43 | 0.2.9.17 | 0.00006324400487756066 | 1 | | trump(a)whitehouse.gov | 0.4.0.5 | 0.0000618066451352206 | 1 | | Webmaster isendemailforyou AT gee mail DOT com | 0.2.9.14 | 0.000057494554539516685 | 1 | | creuss < tor_creuss AT gmx dot de> | 0.2.9.16 | 0.00005605718911283475 | 1 | | buggeroff at goaway dot org 16jtcMMDZBkaopan1fQuPmRQP7N8TGKjuK | 0.2.9.14 | 0.00004599564249474497 | 1 | | Pipo de Clown <tor(a)ouroborus.nl> | 0.4.0.5 | 0.00004599564249474497 | 1 | | wildro(a)hotmail.de | 0.4.0.5 | 0.00004599564249474497 | 1 | | Steve Garcia <steve(a)cs.csubak.edu> | 0.2.9.14 | 0.00004312091448355204 | 1 | | dd tech team <tor-exit AT derechosdigitales dot org> | 0.2.9.16 | 0.00003880882388784812 | 1 | | 1024D/102E81AD jsled <jsled(a)asynchronous.org> | 0.4.0.5 | 0.000033059367865462264 | 1 | | Random Person <auroraborealis AT adelieland dot eu> | 0.4.0.5 | 0.000030184639854269335 | 1 | | Duat Tor <duattor AT gmx dot com> | 0.4.0.5 | 0.000028747277269758342 | 1 | | sderring(a)yahoo.com | 0.2.9.16 | 0.000028747277269758342 | 1 | | admin(at)101000101000(dot)org(dot)uk | 0.2.9.16 | 0.000024435183831883478 | 1 | | golTorNode1 info(a)goldingerit.ch | 0.2.9.16 | 0.000024435183831883478 | 1 | | 0x1ADCBE03 | 0.2.9.16 | 0.00002156045724177602 | 1 | | chris.troutner(a)gmail.com | 0.2.9.15 | 0.00002156045724177602 | 1 | | Admin <tor(a)o-o-o-o-o-o.net> | 0.4.0.5 | 0.000020123093236179557 | 1 | | chris(a)foxearth.org | 0.2.9.16 | 0.000020123093236179557 | 1 | | 0xF94482DF grin < on grin hu > | 0.2.9.16 | 0.000018685729230583092 | 1 | | Otis Otterhound <otis AT waywardhound dot net> | 0.2.9.14 | 0.000018685729230583092 | 1 | | S S <ssmurat76(a)gmail.com> | 0.2.9.16 | 0.000018685729230583092 | 1 | | toragent4054(a)gmail.com | 0.2.9.16 | 0.000018685729230583092 | 1 | | wose <tor AT zuendmasse dot de> | 0.2.9.16 | 0.000018685729230583092 | 1 | | 1024R/0FCE8549 Alexander Oelzant <alexander(a)oelzant.priv.at> | 0.2.9.16 | 0.000015811001219390164 | 1 | | bengamra.raouf7(a)gmail.com | 0.2.9.14 | 0.000015811001219390164 | 1 | | escbutton(a)riseup.net | 0.2.9.16 | 0.000015811001219390164 | 1 | | tcostiou(a)hotmail.com | 0.2.9.16 | 0.000015811001219390164 | 1 | | Tor Kontakt <tor AT anonym dot im> | 0.2.9.16 | 0.000015811001219390164 | 1 | | xak317ne <xak317ne(a)example.com> | 0.2.9.16 | 0.000015811001219390164 | 1 | | yuki(a)minakami.cn | 0.2.9.14 | 0.000015811001219390164 | 1 | | 0x6A49B19728ABDD92 Paul Brossier <piem AT piem dot org> | 0.2.9.16 | 0.000014373638634879171 | 1 | | ihuhubhd1wya google mail | 0.2.9.16 | 0.000014373638634879171 | 1 | | marius+tor(a)psihoexpert.ro | 0.2.9.10 | 0.000014373638634879171 | 1 | | 0xE81A4BBA Kate Dawson <k4t(a)3msg.es> | 0.2.9.16 | 0.000012936274629282707 | 1 | | 0xFFFFFF Harvey Randall <harvey_randall(a)protonmail.com> | 0.2.9.16 | 0.000012936274629282707 | 1 | | Daniel Mansfield <daniel.f.mansfield AT gmail dot com> | 0.4.0.5 | 0.000012936274629282707 | 1 | | echo \"5qYR01x01xdtk\" | sed -e 'y/Yd50qkRt1x/r.twoe@diu/' | 0.2.9.16 | 0.000012936274629282707 | 1 | | Random Person <tormessages AT toy dot xnc dot com> | 0.4.0.5 | 0.000011498910623686243 | 1 | | 0x480049C5107676B5DA4621351FD1F681710CF330 Look it up on http://pgp.mi | 0.4.0.5 | 0.000010061546618089778 | 1 | | 0xD3650780 torclients(a)erhsch.de | 0.2.9.16 | 0.000010061546618089778 | 1 | | info(a)alboh.de | 0.2.9.10 | 0.000010061546618089778 | 1 | | Random Person <abuse(a)bme.hu> | 0.2.9.14 | 0.000010061546618089778 | 1 | | kremidi <kremidi AT tipota dot de> | 0.4.0.5 | 0.000008624182612493314 | 1 | | 0x0E86A81F Mike Gentile <mikeyg AT mac DOT com> | 0.2.9.16 | 0.000005749455311843121 | 1 | | 3F9061452500B8B38AAB6B1816B174717CF1C119DF78CFF48A7C6F5D9BBB6F0E48F185 | 0.4.0.5 | 0.000004312091306246657 | 1 | | fshuc449(a)secure.mailbox.org | 0.4.0.5 | 0.000004312091306246657 | 1 | | Hypnotoad <hypnode AT emailn dot at> | 0.2.9.16 | 0.000004312091306246657 | 1 | | Just Testing <cnrfilter(a)mail.ru> | 0.2.9.16 | 0.0000028747276559215607 | 1 | | 0xFFFFFFFF Random Admin <onionqq AT gmx dot com> | 0.2.9.16 | 0.0000014373638279607803 | 1 | | mail(a)domain.com | 0.4.0.5 | 0.0000014373638279607803 | 1 | +------------------------------------------------------------------------+-------------------+--------------------------+---------+ -- https://mastodon.social/@nusenu

1 1

relayor v20.0.2
by nusenu 31 May '20

31 May '20

Hi, relayor v20.0.2 is released. relayor helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor Changes ------- - add support for OpenBSD 6.7 - add support for Ubuntu 20.04 (drop 18.04) - increase min supported tor version 0.2.9 -> 0.3.5 - increase min. ansible version from 2.9.1 to 2.9.7 Debian 9 (oldstable) support will be dropped before the end of the year, if you use relayor with Debian make sure to run Debian 10. kind regards, nusenu -- https://mastodon.social/@nusenu

3 2

Re: [tor-relays] Fw: So I am moving my bridge to a new OS and have a few questions?
by Keifer Bly 30 May '20

30 May '20

Awesome, thanks! This is very helpful Torix. It's still the same IP address, I wonder if that means the bridge is less effective..... --Keifer On Fri, May 29, 2020 at 5:18 AM <torix(a)protonmail.com> wrote: > Dear Keifer, > > I'm sure the gurus can say exactly what happens in an upgrade, but I can > say that it is the keys in /var/lib/tor/keys that uniquely define your tor > instance. As you did not transfer the keys from the windows box, they were > created anew when you first started up tor, and your box is considered a > new relay. > > I don't think this is a problem, especially as new bridges 1. are needed > for May35th(Tinamann Square) right now, when China usually locks down its > internet "just in case" and 2. bridges gradually get discovered and > blocked, so starting anew is a plus, not a minus. > > HTH, > > --Torix > > > Sent with ProtonMail <https://protonmail.com> Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Friday, May 29, 2020 11:17 AM, Keifer Bly <keifer.bly(a)gmail.com> wrote: > > Hi all, > > So I am switching my OBFS4 bridge that was here > > > https://metrics.torproject.org/rs.html#details/386E99371B8CD938248940B754F1… > > > From running on Windows to running on Debian, as the older computer I was > running it on, Windows updates started causing it to not boot correctly > haha. With some work I was able to get Debian running on the machine. > > I am wondering, does unattended upgrades as configured here: > https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/DebianUbuntuUpd… > > > Keep OBFS4 up to date as well? > > Is it safe to use tor browser through teamviewer from the computer I am > running the bridge on? > > Unfortunately the relay key for the former bridge was lost as the hard > drive failed due to a Windows update causing it to crash, do the > bridge relay keys have any other relevance than flags? > > Thanks very much. > --Keifer > > >

1 0