Thanks for the report, I have forwarded it for removal.
li...@for-privacy.net:
> Wtf, this exit has addresses that do not belong to it!
> https://metrics.torproject.org/rs.html#details/385527185E26937D05E0933DD29FF1699056CAF3
Yes, rerouting exit traffic is a practice we have observed in the past.
On 10/11/20 10:20 AM, nusenu wrote:
> Thanks for the report, I have forwarded it for removal.
>
> li...@for-privacy.net:
>> Wtf, this exit has addresses that do not belong to it!
>> https://metrics.torproject.org/rs.html#details/385527185E26937D05E0933DD29FF1699056CAF3
>
> Yes, rerouting exit t
> I am losing patience with the "let's play nice and let exit IP addresses
> be predictable" model... We are not being treated well by the banhammer
> brigade, and it might be time to flip some tables. I would not call
> simply using a different exit IP than your relay's OR port a bad exit.
I'm no
On 10/11/20 1:17 PM, nusenu wrote:
>> I am losing patience with the "let's play nice and let exit IP addresses
>> be predictable" model... We are not being treated well by the banhammer
>> brigade, and it might be time to flip some tables. I would not call
>> simply using a different exit IP than y
On Sun, Oct 11, 2020 at 01:39:17PM -0500, Mike Perry wrote:
> > I believe I can tell rerouting exits from exits having distinct IPs for
> > inbound and outbound connections - in most cases.
>
> Are your scanners available for others to run? I understand that it is a
> risk that making them public
On 11.10.2020 22:41, Roger Dingledine wrote:
Right, in this particular case, we already run a scanner which provides
public output: it's the tordnsel scanner, and check out
https://check.torproject.org/exit-addresses
Damn it, the boy was hardworking.
ExitNode 385527185E26937D05E0933DD29FF1699
Just woke up. So, whats wrong with some of my relays in this list?
nifty
> On 12. Oct 2020, at 00:13, li...@for-privacy.net wrote:
>
> On 11.10.2020 22:41, Roger Dingledine wrote:
>
>> Right, in this particular case, we already run a scanner which provides
>> public output: it's the tordnsel sc
-
From: tor-relays On Behalf Of
li...@for-privacy.net
Sent: 11 October 2020 23:13
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] BadExit: Rerouting exit relays detected (1)
45.63.11.98
On 11.10.2020 22:41, Roger Dingledine wrote:
> Right, in this particular case, we already
niftybunny:
> Just woke up. So, whats wrong with some of my relays in this list?
some "exit" relay routed its traffic back into tor by using
a tor client. That tor client used exit relays - yours were among them.
So nothing wrong on your side.
signature.asc
Description: OpenPGP digital sig
Dr Gerard Bulger:
> Torrc allows you to exit from a different IP. I thought it a good
> idea to stop arbitrary blocking of the advertised Tor exit IP, the
> captchas and blacklists that tor users suffer. When IPv6 implemented
> fully we have a wide range of IPs to send from on each server.
>
>
On 12.10.2020 15:05, Dr Gerard Bulger wrote:
Torrc allows you to exit from a different IP. I thought it a good
idea to stop arbitrary blocking of the advertised Tor exit IP, the
captchas and blacklists that tor users suffer. When IPv6 implemented
fully we have a wide range of IPs to send from on
11 matches
Mail list logo
