[tor-relays] OrNetStats Update Interval

have any expectations or opinion on how often the stats should be updated on OrNetStats please let me know. Off-list replies are fine as well. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https

[tor-relays] relayor v23.2.0 is released

Hi, relayor v23.2.0 is released. relayor is an ansible role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor#main-benefits-for-a-tor-relay-operator This release includes new prometheus alert rules so you do not forget

[tor-relays] Exit Relays: What is your DNS timeout rate?

_total[15m])) If you run exits without relayor you can use these queries: (sum by (job)(rate(tor_relay_exit_dns_error_total{reason="tor_timeout"}[15m])))/(sum by (job)(rate(tor_relay_exit_dns_query_total[15m])))*100 sum(rate(tor_relay_exit_dns_query_total[15m])) kind regards,

Re: [tor-relays] AROI not getting verified

Thanks for taking the time to setup your AROI. Am I missing something? there is a typo in: "... poof:uri-rsa ..." poof -> proof kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproj

[tor-relays] ContactInfo semantics

information field in arti to just allow an email address kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] torrc ContactInfo

://gitlab.torproject.org/tpo/core/tor/-/blob/aef76beccc6b7422613d1fddc0369eb7c9f558e4/doc/man/tor.1.txt#L2239 kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman

[tor-relays] Tor Relay Operator Poll (closes on 2023-05-30)

but ensure to submit the same random string at the end as you did the first time so they can be linked. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin

Re: [tor-relays] Open call for proposals for improving the health of the Tor relay operator community and the Tor network

the torproject's "self-assessment" on this before I send my opinion on it. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Open call for proposals for improving the health of the Tor relay operator community and the Tor network

er some more fundamental questions, like the one I sent previously, found under "a few questions". I found it surprising to see some of my previous proposals linked on the slides of the meeting - because tor core people (arma, geko, more?) have practically rejected them i

Re: [tor-relays] Open call for proposals for improving the health of the Tor relay operator community and the Tor network

gus: On Fri, Mar 03, 2023 at 11:26:07PM +0100, nusenu wrote: I've got some practical experience with how things are (not) handled by the Tor Project in this space which discourages involvement. The past has also shown that proposals in this area are not handled as tor proposals in the sense

Re: [tor-relays] D5A3882CBDBE4CAD2F9DDA2AB80FE761BEDC3F11 is spoofing my contact info

verification anyway. Watch out for more false friends. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Open call for proposals for improving the health of the Tor relay operator community and the Tor network

ntributors to join our network. Will there be a longer problem statement and a description of your threat model? adopted by a meaningful fraction of the Tor community (e.g. providing valid contact information). Can you elaborate on how you define "valid" in this co

[tor-relays] removing tor versions from "recommended versions" before they reach EOL

they reach their eol date so relay operators get to see a log entry and have some time to react. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman

[tor-relays] disable moderation on tor-relays again?

Hi, can we try to disable moderation on this list again and see how it goes? If it gets out of hand you can always move back to a moderated mode or a mode where the first email of a sender is moderated. kind regards, nusenu -- https://nusenu.github.io

Re: [tor-relays] Use OutboundBindAddress on multi-instance tor servers

.ip_local_port_range="64000 65535" I don't think that it is a good approach to set such a low hard limit for connections to any single destination. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torp

[tor-relays] HowTo use relayor's Prometheus Integration (relayor v23.1.0)

for prometheus. This includes a few backward incompatible changes. Full Changelog: https://github.com/nusenu/ansible-relayor/releases/tag/v23.1.0 With the release I also published this guide that should help users get started with relayor's prometheus integration: https://github.com/nusenu/ansible

[tor-relays] publish current AuthDirMaxServersPerAddr limit?

Hi, would it be possible to publish the currently enforced value of AuthDirMaxServersPerAddr on some tpo website? Maybe consensus-health.tpo? kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org

Re: [tor-relays] Use OutboundBindAddress on multi-instance tor servers

multi-instance tor relay Can you please describe what that is? The subject uses the more correct term 'multi-instance tor server'. A single OS running more than one tor relay instance. In the context of this email, more specifically running more than 2 tor relays. kind regards, nusenu

[tor-relays] Use OutboundBindAddress on multi-instance tor servers

, no further action required. https://github.com/nusenu/ansible-relayor/blob/2bc62d62f85b62c51a38d9caa893ab0fadbfff01/templates/torrc#L7 kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https

Re: [tor-relays] Questions about 4 Relays per IP and the ddos mitigation scripts

-for-Relay-Operators At the very least relays blocking/dropping some packets of other relays should be very transparent about it. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https

Re: [tor-relays] Questions about 4 Relays per IP and the ddos mitigation scripts

vise against filtering practices between relays. The first step should always be on a social level: Try to reach the operator if you feel they attack your relay and NOT iptables DROP without notice. kind regards, nusenu -- https://nusenu.github.io ___ to

[tor-relays] relayor v23.0.0 is released

Hi, relayor v23.0.0 is released. relayor is an ansible role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor#main-benefits-for-a-tor-relay-operator This release comes with some great new prometheus integration features

[tor-relays] relayor v22.2.1 is released

Hi, relayor v22.2.1 is released. https://github.com/nusenu/ansible-relayor/releases/tag/v22.2.1 relayor is an ansible role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor#main-benefits-for-a-tor-relay-operator

[tor-relays] actively maintaining 'recommended versions' list (was: Tor 0.4.6.x is unsupported, please upgrade)

In the past one of the first steps was to update the 'recommended versions' at dir auths so operators get to see an indicator on Relay Search and in their logs if they run old versions of tor, even if they do not have any usable ContactInfo that can be used to potentially reach them. dir

Re: [tor-relays] When will relays disappear form tor metrics

When can I expect they will disappear from tor metrics? 7 days after their last seen date -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] tor 0.4.6 reached end of life

If you still run tor 0.4.6, now is a good time to upgrade your tor version. the list of largest operators still running end of life tor versions: https://nusenu.github.io/OrNetStats/#end-of-life-relays-share -- https://nusenu.github.io ___

[tor-relays] relayor v22.2.0-rc is released

Hi, relayor v22.2.0-rc is released. relayor is an ansible role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor#main-benefits-for-a-tor-relay-operator Changes since relayor v22.1.0-rc: https://github.com/nusenu/ansible

Re: [tor-relays] New OrNetStats Section: Largest Bridge Operators

li...@for-privacy.net: Oh nice, thanks. I just saw that nusenu also thought of us 'proof:dns-rsa' users. ;-) https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/#dns-rsa For bridges: hashed-fingerprint.example.com value: “we-run-this-tor-bridge” thanks for properly

Re: [tor-relays] Relay migration: best practices?

permissions are set properly - start tor on the new server Compared to only copying the key files, this will avoid tor assuming it is a new relay without prior history. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor

[tor-relays] New OrNetStats Section: Largest Bridge Operators

be extended to support bridges. kind regards, nusenu [1] https://nusenu.github.io/OrNetStats/#authenticated-relay-operator-ids -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman

Re: [tor-relays] Tor 0.4.7.7 Segmentation fault on Ubuntu 22.04 caused by "rseq"

https://gitlab.torproject.org/tpo/core/tor/-/issues/40601 ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Reduced exit and not IPv4 exit traffic at all

only works. AFAIK, exits must have at least port 80,443 and 53 open on IPv4. You can run a relay that does allow exiting to IPv6 and not IPv4 but it will not get the exit flag. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing

Re: [tor-relays] TorWeather replacement

even when it does not provide hourly granularity, but feel free to share your opinion if you agree/disagree. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin

[tor-relays] TorWeather replacement features

lnerable/end-of-life tor release - relay lost guard/exit flag The first notification method will be email. How important would be matrix as a second notification method to you? Would you use one or multiple notification methods at the same time? kind regards, nus

Re: [tor-relays] Genereal queations about MyFamily

y that of the Family as such? Are there already suggestions for this with the developers? A new MyFamily design is in the works, which will be easier to configure for operators https://lists.torproject.org/pipermail/tor-relays/2021-November/019954.html Like with AROI from nusenu. To avoid misund

Re: [tor-relays] reminder: tor 0.3.5 reaches end of life on 2022-02-01

650 tor relays (>5% consensus weight) are still running tor 0.3.5.x. Are your relays affected? https://nusenu.github.io/OrNetStats/#end-of-life-relays-share please upgrade to a supported tor release. -- https://nusenu.github.io ___ tor-relays mailing

Re: [tor-relays] Outdated GeoIP DB

, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] reminder: tor 0.3.5 reaches end of life on 2022-02-01

, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays ___ tor-relays mailing list tor-relays

[tor-relays] relayor v22.1.0-rc is released

will come with a guide on how to use all the new prometheus integrations in relayor. https://github.com/nusenu/ansible-relayor/releases/tag/v22.1.0-rc The relayor GitHub repo has now Discussions enabled. Changes since relayor v22.0.0-rc: * add support for prometheus blackbox_exporter scrape

Re: [tor-relays] General overload -> DNS timeouts

curity/tor/ After upgrading the tor version the overload indicator on will disappear when it it was DNS related (there can be other reasons). kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject

[tor-relays] relayor v22.0.0-rc is released

Hi, relayor v22.0.0-rc is released. relayor is an ansible role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor#main-benefits-for-a-tor-relay-operator Changes since relayor v21.2.0-rc: * MetricsPort support

Re: [tor-relays] Incorrect "first seen" info

Hi, could you paste the Relay Search page link and state the correct and incorrect first_seen timestamps? kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi

[tor-relays] Tor related talks @ rC3

in chronological order: -- title: Towards a more Trustworthy Tor Network when: 2021-12-28, 17:00 CET where: https://streaming.media.ccc.de/rc3/csh primary target audience: - Tor user - Tor relay operators - onion service operators - and

Re: [tor-relays] General overload -> DNS timeouts

ow since the stable repo has been updated to tor 0.4.6.9 and the experimental repo contains 0.4.7.3-alpha which also includes your desired change. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.o

Re: [tor-relays] General overload -> DNS timeouts

the Torproject's Debian repos since these versions are usually not "swiftly" available on deb.torproject.org yet (unless you switch to nightly packages which I wouldn't recommend). currently: Version: 0.4.6.8-1~d10.buster+1 [1] kind regards, nusenu [1] https://deb.torproject.org/torproject

Re: [tor-relays] General overload -> DNS timeouts

To stop confusing operators it would make sense to remove the "This relay is overloaded since" banner from Relay Search for all tor versions prior to 0.4.6.9 and 0.4.7.3-alpha, no? kind regards, nusenu -- https://nusenu.github.io ___

Re: [tor-relays] 122 Qimam Relays and Bridges

I was wondering whether this was the first actual case where someone exploited vulnerabilities at a wordpress website to place the CIISS v2 proof file on someone else's webserver. To investigate that suspicion I reached out to the Qimam organization (not using the gmail address) the same day

Re: [tor-relays] [Looking for feedback] An easier way to declare families

Nick Mathewson: 1) The proposal currently limits each relay to no more than 3 families. Is that a reasonable upper bound? Yes, 3 is a reasonable limit. 2) We hadn't been planning to implement multi-family support right away, though I could if needed. Is that something that many

Re: [tor-relays] Introduction from lokodlare

-Sharing-Specification/#hoster kind regards, nusenu btw: thanks for setting up the CIISS v2 fields including the proof on your relays https://nusenu.github.io/OrNetStats/lokodlare.com.html -- https://nusenu.github.io ___ tor-relays mailing list tor

[tor-relays] MyFamily bridge support

Regarding MyFamily, there's a new MyFamily proposal that will include bridges, please check this thread and spec: https://gitlab.torproject.org/tpo/core/torspec/-/blob/main/proposals/321-happy-families.md https://lists.torproject.org/pipermail/tor-relays/2021-November/019954.html the related

Re: [tor-relays] Rejected-fingerprints-found-in-attacks wiki page

us. it would give users of these lists the possibility to consume it in a much more trivial way without having understand the semantics of the wiki page curl https://gitlab/$lastmonth-rejection-file kind regards, nusenu -- https://nusenu.github.io ___

[tor-relays] Rejected-fingerprints-found-in-attacks wiki page

are included in the dir auth config) -MM - have a monthly cronjob that copies and pushes the priors month file into a public git repository kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https

[tor-relays] Rerouting exit relays detected - EXNODE35037

BadExit: Rerouting exit relays detected (1) The following exit relays are routing their traffic back into the tor network: nickname: EXNODE35037 First seen: 2021-11-22 15:00:00 Consensus weight: 1 AS: ITL LLC OR IP address: 195.123.220.84 Exit addresses: 185.220.101.138 195.123.220.84

[tor-relays] relayor v21.2.0-rc is released: prometheus exporter support

Hi, relayor v21.2.0-rc is released. relayor is an ansible role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor#main-benefits-for-a-tor-relay-operator NOTE: This release contains a backwards incompatible change

[tor-relays] OverloadStatistics man page

Arlen Yaroslav via tor-relays: The undocumented configuration option 'OverloadStatistics' related: https://gitlab.torproject.org/tpo/core/tor/-/issues/40504 -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org

Re: [tor-relays] General overload -> DNS timeouts

Anders Trier Olesen: The Tor relay guide should recommend running your recursive resolver (unbound) on a different IP than your exit: https://community.torproject.org/relay/setup/exit/ yes, that is a good idea, here is a PR for it: https://github.com/torproject/community/pull/169/files

Re: [tor-relays] A Simple Web of Trust for Tor Relay Operator IDs

her to trust a given relay and I don't want to manually link relays to their operator (have done that before and don't want to go back to that ;). you have some other input factors in your trust scheme and you prefer to manually maintain a database with relay IDs + trust info.

Re: [tor-relays] General overload -> DNS timeouts

t tor reports. Once you have MetricsPort setup and graphs for the data you can try to adapt the DNS settings or tune your resolver and see if things improve (timeout rate goes down). kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mai

Re: [tor-relays] [Looking for feedback] An easier way to declare families

by many of the largest families: I'll certainly integrate option 3 in relayor. When compared with option 0 (current MyFamily design) option 2 has weaker properties so I would stay on option 0 until option 3 becomes available. kind regards, nusenu -- https://nusenu.github.io

Re: [tor-relays] known issues with deb.torproject.org repos?

David Goulet: On 29 Oct (00:51:15), nusenu wrote: Hi, are there known issues with the nightly master debian package builds? https://deb.torproject.org/torproject.org/dists/ Not to our knowledge? I'm using nightly-master in ansible-relayor CI runs and noticed the version says currently

Re: [tor-relays] torproject forum

I'v moved the discussion to tor-talk since it is about more then just tor-relays: https://lists.torproject.org/pipermail/tor-talk/2021-October/045779.html -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org

[tor-relays] known issues with deb.torproject.org repos?

? (as it used to be) https://gitlab.torproject.org/tpo/core/team/-/wikis/NetworkTeam/CoreTorReleases#current kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin

Re: [tor-relays] Relay operator section in our forum

nusenu: [1] https://forum.torproject.net/ [2] https://forum.torproject.net/c/support/relay-operator/17 thank you for creating the Discourse forum. I've to admit I'm a bit surprised the torproject has chosen the Discourse Saas option instead of running it on a system where you control what

Re: [tor-relays] Relay operator section in our forum

than the current "Relay Operator" name (singular). kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] relayor v21.1.0 is released

Hi, relayor v21.1.0 is released. relayor is an ansible role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor Changes since relayor v21.0.1 https://github.com/nusenu/ansible-relayor/releases/tag/v21.1.0 - generate

Re: [tor-relays] A Simple Web of Trust for Tor Relay Operator IDs

f malicious tor network capacity. """ but I don't understand how *publishing* that information is supposed to limit malicious relays. you are right, publishing it alone does not change anything it is just the important first step. I updated the text to make this part clearer

Re: [tor-relays] A Simple Web of Trust for Tor Relay Operator IDs

/tpo/core/torspec/-/merge_requests/49 kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] A Simple Web of Trust for Tor Relay Operator IDs

Hi, I wrote down a spec for a simple web of trust for relay operator IDs: https://gitlab.torproject.org/nusenu/torspec/-/blob/simple-wot-for-relay-operator-ids/proposals/ideas/xxx-simple-relay-operator-wot.md#a-simple-web-of-trust-for-tor-relay-operator-ids This is related to: https

Re: [tor-relays] tor version question

: 0.4.6.6 and 0.4.5.10 EPEL 8 has tor version 0.4.5.10 which is also fine. https://bodhi.fedoraproject.org/updates/?packages=tor kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https

Re: [tor-relays] Need help with Dir Address and Exit Address

t an issue since dir fetches happen via the OR port these days. If you want to have a dir address make sure that your config includes a DirPort line and that the given port is reachable. Also checking your logs is a good next step. kind regards, nusenu -- https://nusenu.github.io [1] https://me

[tor-relays] OrNetStats now parses all your ContactInfo v2 fields and warns you if your Tor version is vulnerable

kind regards, nusenu [1] https://github.com/tempname1024/allium [2] https://nusenu.github.io/ContactInfo-Information-Sharing-Specification -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject

[tor-relays] new tor network graphs on OrNetStats

a better view / understanding about what is happening/changing on the tor network infrastructure. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman

Re: [tor-relays] Relay Control Port

, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] >50% tor exit capacity is now safer against ContactInfo impersonation attacks

he short version on how to set a verifiable domain in your ContactInfo: https://mastodon.social/@nusenu/106094297537909911 Thanks to everyone who joined so far and indirectly helps with malicious relay analysis! kind regards, nusenu -- https://nusenu.github.io _

[tor-relays] relayor v21.0.1 is released

Hi, relayor v21.0.1 is released. relayor is an ansible [1] role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor [1] https://www.ansible.com/ changes since relayor v21.0.0 * install the gpg package by default

Re: [tor-relays] significant decrease in onionoo AS data coverage after switch to ipfire geoip db?

automatically) and allow users to easily learn when you update and what version you use. Thanks for improving onionoo's ASN data. kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https

[tor-relays] end of life: tor 0.4.4 (2021-06-15)

Reminder: tor 0.4.4 reached it's end of life on 2021-06-15. Over 1000 relays and about 20% of the network capacity runs an unsupported version of tor. https://gitlab.torproject.org/tpo/core/team/-/wikis/NetworkTeam/CoreTorReleases#end-of-life Consider upgrading if you are one of the affected

[tor-relays] significant decrease in onionoo AS data coverage after switch to ipfire geoip db?

things worse? ++--+ | 2021-06-10 | 419 | | 2021-06-11 | 422 | | 2021-06-12 | 422 | | 2021-06-13 | 424 | | 2021-06-14 | 421 | | 2021-06-15 | 422 | | 2021-06-16 | 420 | | 2021-06-17 | 414 | | 2021-06-18 | 1748 | kind regards, nusenu

Re: [tor-relays] New Test for Measuring the Accuracy of Tor Relays' Advertised Bandwidths

The effect of these measurements is visible in significant (temporary) "increase" of adv. bw visible on metrics: https://metrics.torproject.org/bandwidth.html?start=2021-04-20=2021-05-21 and on the OrNetStats per operator graphs, this is a good example:

[tor-relays] say hi (and goodbye) to >1000 new exit relays at OVH

OVH is really popular these days... +-+-+--+-++ | first_seen | contact | nickname | IP | FP | +-+-+--+-++ | 2021-05-03 04:00:00 | NULL| Unnamed

Re: [tor-relays] Wrong country relay

they are in the process to update the geoip database that will solve this issue. you can follow the gitlab issue here: https://gitlab.torproject.org/tpo/metrics/relay-search/-/issues/40004 -- https://nusenu.github.io ___ tor-relays mailing list

Re: [tor-relays] let's make ContactInfo mandatory for exits (and warn others)

>> I propose to make torrc's ContactInfo mandatory for exit relays with >> the following timeline: > > With respect nusenu, exactly what is your relationship to the Tor > project? To be clear: I'm not a member of the Tor Project and I don't claim to be one. > Ar

Re: [tor-relays] let's make ContactInfo mandatory for exits (and warn others)

a person to be linked to their tor relay. My email was also intended to let exit operators know that they might notice less traffic in the near future on exits that have no contactinfo. kind regards, nusenu -- https://nusenu.github.io ___ tor-relay

[tor-relays] TorBrowser HTTPS-Only Mode

> (FWIW: on the client side there is still the HTTPS-only mode in the > pipeline, which could easily be a game-changer here, too.) Is the torproject backporting https-only mode [1] to 78esr / Tor Browser? kind regards, nusenu [1] https://blog.mozilla.org/security/2020/11/17/fire

Re: [tor-relays] let's make ContactInfo mandatory for exits (and warn others)

Hi Toralf, Toralf Förster: > On 4/24/21 12:11 PM, nusenu wrote: >> * tor 0.4.7: no longer assign the exit flag to relays not having a >> ContactInfo (< 5 chars) in their descriptor. >> Log a warning for relay operators, > > I've opened 1-2 dozen ports -

Re: [tor-relays] how does one file a problem report?

Scott Bennett: > Would someone please point me to the > relevant information? Bugzilla seems to be much easier to use. If you want to report a bug in tor: go to core -> tor -> issues -> New issue https://gitlab.torproject.org/tpo/core/tor/-/issues/new?issue%5Bassignee_id%5D=%5Bmilestone_id%5D=

[tor-relays] let's make ContactInfo mandatory for exits (and warn others)

one result in exits getting non-empty ContactInfos. More details will follow soon. kind regards, nusenu -- https://nusenu.github.io OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.

Re: [tor-relays] malicious exit relays by andrejgvozde...@gmail.com

emoval in their logfiles anyway but we tor users don't get to learn anything because it remains largely invisible to us. Roger's email from 2020-10-31 is a good example that made further investigations possible. kind regards, nusenu -- https://nusenu.git

Re: [tor-relays] malicious exit relays by andrejgvozde...@gmail.com

9E3BD96CE87439753A > B1896E58FDEB5627B6B8334E6ABD42767AB8B0D9 after confirming with the hoster that you were and are in fact their customer at these and other IPs used by malicious tor relays, I was wondering whether you wanted to comment on that? Especially since you recently added more exit relays. kind regar

[tor-relays] Relay Search without AS number/name information?

on it. kind regards, nusenu [1] https://gitlab.torproject.org/tpo/core/tor/-/issues/40224 [2] https://location.ipfire.org/ -- https://nusenu.github.io OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays

[tor-relays] relay impersonation (contactinfo)

Search you can do so using "contact:searchstring" Be creative in your search terms. This even makes sense if you do not run relays at all but your name is somewhat known in this context. kind regards, nusenu Forwarded Message Subject: tor relays rosiwig429(at)lid

[tor-relays] relayor v21.0.0 is released

Hi, relayor v21.0.0 is released. relayor is an ansible [1] role that helps you with running tor relays with minimal effort (automate everything). https://github.com/nusenu/ansible-relayor [1] https://www.ansible.com/ This version contains a bugfix: * the GPG key for deb.torproject.org

Re: [tor-relays] Exit relay operators please help test #2667 branch

Roger Dingledine: > On Fri, Jan 29, 2021 at 12:34:28AM +0100, nusenu wrote: >> If dir auths (some or all) are willing to share (privately or publicly) the >> distribution of >> attack load (frequency, bandwidth, ...) by exit source IP in total or >> relative values &

Re: [tor-relays] Exit relay operators please help test #2667 branch

Unless you already ruled out that hypothesis by looking at the attack distribution by source IP: If dir auths (some or all) are willing to share (privately or publicly) the distribution of attack load (frequency, bandwidth, ...) by exit source IP in total or relative values I can correlate this

Re: [tor-relays] OrNetStats: Operator Level Graphs added

; 2021-01-13 21:40 GMT, nusenu : >>> OK. Unfortunately I can only redirect in private webspace. And that >>> is "MUST NOT". My DNS-TXT records are slowly spreading across the DNS >>> world. In a few days my 'proof' should show up on OrNetStats. >> >&

Re: [tor-relays] OrNetStats: Operator Level Graphs added

> OK. Unfortunately I can only redirect in private webspace. And that > is "MUST NOT". My DNS-TXT records are slowly spreading across the DNS > world. In a few days my 'proof' should show up on OrNetStats. The DNS record check will be added in a few days, at that point your relays and a few more

Re: [tor-relays] OrNetStats: Operator Level Graphs added

sed more efficiently, no? After learning that these are not starting at 0, things should be clear. What doesn't make sense for me: negative ranges, which I'll try to address soon. thanks for your input, nusenu ___ tor-relays mailing list tor-relays@lists.torpr

Re: [tor-relays] OrNetStats: Operator Level Graphs added

s many hosters as you like. kind regards, nusenu -- https://nusenu.github.io OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] OrNetStats: Operator Level Graphs added

n the DNS. Would like to have as little software or > services as possible on the relays. just to clarify: there is no requirement to run additional software on the relay. the url can point to an arbitrary domain that you manage. kind regards, nusenu OpenPGP_signature Descri

Re: [tor-relays] OrNetStats: Operator Level Graphs added

Toralf Förster: > On 1/9/21 9:38 PM, nusenu wrote: > >> 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. > cool idea, > >

  1   2   3   4   5   6   7   8   9   10   >