Re: [tor-relays] Discuss. Why not split donations to Tor relay owners?
> Am 01.11.2023 um 17:53 schrieb dewaj : > [...] > Who wants to be identified as a tor user, let alone a relay operator? > […] I don't like this attitude at all and I don't think it goes with the demands of most operators either. I have often heard on this list and elsewhere sentences like: "It is an act of anonymity to use Tor. It is an act of transparency to operate Tor relays." I agree with this completely. Tor relay operators should always be responsive and have no problem saying who they are. If there are problems with a relay that are criminally relevant, the company running the server will hand over the operator's data to the authorities anyway. Martin signature.asc Description: Message signed with OpenPGP ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Relay in Japan being marked as a US relay?
Hello, unfortunately this happens more often. you are not alone :-) > Am 18.01.2024 um 20:50 schrieb NodNet : > > I think tor and Tor Project use IPFire's DB for GeoIP lookups, and > 198.13.48.219 shows the following: Yes, libloc/location is used. I had the same problem with one or two relays years ago. This was then fixed by a manual override. This is currently also the case with 3 of my relays (37.252.255.135 / 37.252.254.33 / 217.146.2.41) However, I can't explain why. Because the hoster has a geofeed (https://opengeofeed.org/feed/as42473.html) and RIPE also has the correct country information. In any case, it is not so important to me that it is correct in the metrics. But it would be nice. Maybe I'll get round to mentioning it again on the location mailing list soon. Ahoy, Martin ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Relay in AT marked as DE in metrics
>> I have a relay on 152.53.17.183 / 2a0a:4cc0:1:1333::beef which is listed as >> "German" in metrics.torproject.org, but actually it is in Austria > > Was just a topic here recently: > https://lists.torproject.org/pipermail/tor-relays/2024-January/021472.html > > Ask geofeed from the provider and submit a bug report. Your address is in netcups AS. We publish the geofeed here: https://opengeofeed.org/feed/as197540.html (CSV: https://opengeofeed.org/feed/as197540.csv) There you can also see that your network is correctly labelled as an Austrian IP in the geofeed: 152.53.16.0/22 the geofeed is also always kept up to date as it is stored at RIPE: https://apps.db.ripe.net/db-web-ui/query?searchtext=152.53.17.183 -- ahoy, Martin ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] bridges for Lox
>> On 27 Feb 2024, at 15:39, boldsuck wrote: >> On Dienstag, 27. Februar 2024 14:52:00 CET Corl3ss via tor-relays wrote: >>> On 26/02/2024 21:03, Toralf Förster via tor-relays wrote: On 2/26/24 20:07, meskio wrote: > At the moment we're > looking for 10 new bridges for Lox. If it has to be done quickly, I can also deploy the other 4. 9 left >>> >>> And one more added, so 8 left. >> +1 = 7 left > > Added one. 6 left. 4 left. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Archive key from deb.torproject.org was renewed!
Hi, >> wget >> -qO-https://deb.torproject.org/torproject.org/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.asc >> | gpg --dearmor | tee /usr/share/keyrings/tor-archive-keyring.gpg >> >/dev/null > > Is the name important? I assume it's Debian? The onfiguration of the signing key and the repo is configured in Debian (and Ubuntu?) via source.list, see $man 5 sources.list. In most cases this will look something like this: $ cat /etc/apt/sources.list.d/tor.list deb [signed-by=/usr/share/keyrings/tor-archive-keyring.gpg] https://deb.torproject.org/torproject.org bookworm main deb-src [signed-by=/etc/apt/trusted.gpg.d/tor-archive-keyring.gpg] https://deb.torproject.org/torproject.org bookworm main You can place the key anywhere that ‘apt’ can access, you only need to change the path in the source file. Note, however, that for keys that are not managed by a package or the package manager itself, they should be stored either in /usr/share/keyrings or /etc/apt/keyrings. however, you can also overwrite the existing key. I'm not a fan of this and still keep all (old) versions in the keyring.. Since you are all tinkering with your servers anyway, why don't you try deb822-style ;-) $ cat /etc/apt/sources.list.d/tor.sources Types: deb deb-src URIs: tor+http://apow7mjfryruh65chtdydfmqfpj5btws7nbocgtaovhvezgccyjazpqd.onion/torproject.org URIs: https://deb.torproject.org/torproject.org Suites: bookworm Components: main Architectures: amd64 Signed-By: /etc/apt/keyrings/A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89.gpg Ahoy, Martin signature.asc Description: Message signed with OpenPGP ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Archive key from deb.torproject.org was renewed!
>> Since you are all tinkering with your servers anyway, why don't you try >> deb822-style ;-) > > Because that doesn't make sense for public Tor nodes, but rather for .onion > services. > Many ISPs and providers have a Debian and Tor mirror and I use them via > clearnet because reliability for security updates is important to me. ok, you are probably referring to the fact that i use the repo via .onion. But i actually wanted to point out the format of the APT source files, see https://manpages.debian.org/unstable/apt/sources.list.5.en.html#DEB822-STYLE_FORMAT :-) And regardless of that: In my opinion, it makes perfect sense to also obtain public services such as OS updates via Tor. The more data flying around the Tor network, the better it is for the Tor network. Ahoy, Martin ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
