- tor-relays - lists.torproject.org

OrNetStats: Operator Level Graphs added
by nusenu 18 Jan '21

18 Jan '21

Hi, I've added new operator level pages with an interactive graph showing the aggregated guard/exit probability and advertised bandwidth over time across all relays for a given operator. This should allow you to see whether your bandwidth and fractions are growing or decreasing. You can - zoom within the graph to a specific time window (horizontal drag and drop), - change the scale on the y axis (vertical drag and drop) - zoom to a specific area (by selecting a rectangle) or use the preset time frames (week, month, year, ..). To give you a better idea of what these graphs look like, here is an example: https://nusenu.github.io/OrNetStats/www.f3netze.de.html The data source for these graphs is onionoo (torproject.org) it starts at 2019-10-31. The data granularity is about one value per day. kind regards, nusenu -- https://nusenu.github.io

7 18

Bridge Setup
by San Shi 13 Jan '21

13 Jan '21

Hello, I'm following the bridge setup for windows after not being able to start a tor browser for some reason and having some difficulty with the last step. After running tor.exe -f torrc, there is no notice file appearing where it should be, and Tor still seems to fail to setup. In the torrc.txt file I modified the "ORPort TODO1" and "ServerTransportListenAddr obfs4 0.0.0.0:TODO2" by replacing TODO1 and TODO2 with numbers greater than 1024 and less than 9000. I assume either I messed up modifying the text file or that the obsf4 port I selected is not reachable. Using the provided reachability test I tried ~15 4 digit numbers, using 0.0.0.0 as the IP and a 4 digit number in the appropriate range for the obsf4 port (none reachable). Any suggestions? Thanks!

3 2

Introducing new bridge status page
by Philipp Winter 12 Jan '21

12 Jan '21

As part of our ongoing effort to reimplement BridgeDB, we now have a bridge status page that shows if a bridge's pluggable transports work: https://bridges.torproject.org/status?id=FINGERPRINT FINGERPRINT is your bridge's fingerprint or its hashed fingerprint -- either works. The backend tests bridges every 18 hours by making a tor process fetch the bridge's descriptor. Tor bridges will soon log a URL pointing to this status page: https://gitlab.torproject.org/tpo/core/tor/-/issues/30477 As of today, 89% of all pluggable transports work. Cheers, Philipp

3 3

My relay software gets hung up on OVH
by Keifer Bly 11 Jan '21

11 Jan '21

2 1

Exit node in spain
by irr4z 11 Jan '21

11 Jan '21

Hello, everybody, Quickly, I write from Barcelona, I am interested in contributing to tor with exit nodes, but I am concerned about legal issues. I see that there is only 1 active exit node in Spain, and I wonder if it is so dangerous in my country :-) Any comment or feedback is welcome. Thanks and beers to everyone! Irr4z

4 5

Config question
by r1610091651 11 Jan '21

11 Jan '21

Hi Recently upgraded to 4.4.6 and noticed new (for me) entry in tor logs: Jan 11 09:24:28.000 [notice] While bootstrapping, fetched this many bytes: This message gets repeated every 6 hours, while there is little extra info added, as it relates to bootstrap / start-up process. I already have "AvoidDiskWrites 1" active in torrc. Is there a way to disable this extra logging? Thanks

1 0

Some ContactInfo Spec Adoption Stats
by nusenu 06 Jan '21

06 Jan '21

Hi, it is great to see that just 2-3 months after publishing version 2 of the ContactInfo Information Sharing Spec [1] there are already over 100 tor relays (>10% exit probability) making use of it, to allow for automated verification of the url field in the ContactInfo. If you are still using version 1 of the spec I'd encourage you to update to version 2, which usually isn't a big effort. Due to the adoption I also started to add stats for it to OrNetStats, but since the proofs and ContactInfo strings are public, everyone can verify it: https://nusenu.github.io/OrNetStats/#verified-operator-domains Currently it does only consider the well-known URI proofs (the DNS proof will also be added). It is also important to note that a verified domain does not say anything about the intentions of an operator, it just prevents things like [2] where a malicious entity claimed to be some other operator by using their ContactInfo without a good automated method to tell them appart, especially if MyFamily is not properly set. And it will also make things easier when tagging relays as "known" or "unknown" [3], since it allows tagging on an operator level instead of trying to figure out who the real operator behind each and every relay is, by using unverified ContactInfo claims manually. In the near future I'd like to make use of the data to generate operator level time series graphs and overall stacked graphs. If you would like to play with the ContactInfo strings yourself, here is an early parser: https://github.com/erans/torcontactinfoparser In the past we had a small error in the generator (field name "gpg:..." was used instead of "pgp:...") this has been fixed: https://torcontactinfogenerator.netlify.app/ kind regards, nusenu [1] https://lists.torproject.org/pipermail/tor-relays/2020-October/019024.html [2] https://lists.torproject.org/pipermail/tor-relays/2020-October/019045.html [3] https://gitlab.torproject.org/tpo/metrics/relay-search/-/issues/40001 -- https://mastodon.social/@nusenu

1 0

consensus
by Felix 06 Jan '21

06 Jan '21

Hi https://consensus-health.torproject.org/consensus-health shows: Consensus was published 2021-01-06 05:00:00 UTC. Unusual Authorities: moria1 Consensus could not be retrieved dizum Consensus could not be retrieved gabelmoo Consensus could not be retrieved maatuska Consensus could not be retrieved faravahar Consensus could not be retrieved longclaw Consensus could not be retrieved bastet Consensus could not be retrieved When I try http://authorityip:dirport/tor/status-vote/current/consensus.z it's 'failed: Operation timed out' What works is: http://relayip:dirport/tor/status-vote/current/consensus.z Am I missing something and is everything good? A glitch? -- Cheers, Felix

2 1

Exit node on Contabo
by Nuno Rego 05 Jan '21

05 Jan '21

> Short experience at Contabo. After 10 days, and after the first abuse complaint of. > > " > Dear Mr Rego, > > Thank you for your reply. > > Generally, it is not denied to use TOR nodes on our services. However, in case it cannot be ensured that those services will not be misused, we have to ask to remove the service from our network. We also included a rule in our terms of services, please see here: > > § 10 Limitation regarding content > > (5) The Provider reserves the right to immediately suspend of any server or webspace package on which any kind of proxy service, such as VPN or TOR, is operated, for which the Provider has knowledge of abuse or fraudulent or unlawful use. > > Please come back within given time frame (you still have 18 hours left) and confirm that you have removed the TOR node. After that we can close this abuse case. > > Thank you for your cooperation. > > If you have any questions or need help, please do not hesitate to contact us. > > -- > Best regards / Mit freundlichen Grüßen, > > Anneli Ulfig > Kundenservice / Customer support > > Contabo GmbH > Aschauer Straße 32a > 81549 München > https://contabo.com> " > > Cumprimentos; -- Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: https://tutanota.com

3 2

Info from my ISP about investigation of tor exits
by Olaf Grimm 03 Jan '21

03 Jan '21

Here is the original of mail (in copy) from my provider Mail copy: "Hello, Unfortunately your traffic type is full of unwanted events not compatible with our company ethic. Since the first date of activity we've received many abuse reports regarding bruteforce, layer7 attacks, hacking and many others. Currently there is a police investigation regarding one of the 2 servers related to hacking activity against an european country security. The access and content is in interpol custody and we have a restriction on reactivation. Kind regards, George Oprea 24/7 Technical Support Zetservers.com /Romania" --> My answer: Thank you for your information. Good luck. I change my other servers to less trouble. (Change Exits to Relay) Olaf

4 3