Re: [tor-relays] BadExit: Rerouting exit relays detected (1) 45.63.11.98

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

Re: [tor-relays] BadExit: Rerouting exit relays detected (1) 45.63.11.98

- 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

Re: [tor-relays] BadExit: Rerouting exit relays detected (1) 45.63.11.98

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

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 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

Re: [tor-relays] BadExit: Rerouting exit relays detected (1) 45.63.11.98

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

Re: [tor-relays] BadExit: Rerouting exit relays detected (1) 45.63.11.98

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

Re: [tor-relays] BadExit: Rerouting exit relays detected (1) 45.63.11.98

> 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

Re: [tor-relays] BadExit: Rerouting exit relays detected (1) 45.63.11.98

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

Re: [tor-relays] BadExit: Rerouting exit relays detected (1) 45.63.11.98

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

Re: [tor-relays] BadExit

Hi Georg, > On 27 Mar 2020, at 22:40, Georg Koppen wrote: > >> (If the DNS for the site they are testing has both IPv4 and IPv6, then >> the outcome will depend on their tor version and config. 0.4.3 and >> later will prefer IPv6 by default.) > > Not sure what Arthur is running but I am just

Re: [tor-relays] BadExit

This. Port 22 especially is a nightmare. niftybunny > On 27. Mar 2020, at 16:29, Toralf Förster wrote: > > Signed PGP part > On 3/27/20 2:17 PM, ger...@bulger.co.uk wrote: >> I have been free of abuse complaints and copyright claims for two years now. > Well, the main problem here fore me is

Re: [tor-relays] BadExit

On 3/27/20 2:17 PM, ger...@bulger.co.uk wrote: > I have been free of abuse complaints and copyright claims for two years now. Well, the main problem here fore me is to get complaints from my hoster itself b/c any open address range are abused soon for port scans -- Toralf signature.asc

Re: [tor-relays] BadExit

: [tor-relays] BadExit teor: > Hi, > >> On 27 Mar 2020, at 02:00, niftybunny >> wrote: >> >> My bad. Never seen this before. I there a good reason for the accept >> 133.0.0.0/8:80 ? >> >>> On 26. Mar 2020, at 15:06, ger...@bulger.co.uk wro

Re: [tor-relays] BadExit

teor: > Hi, > >> On 27 Mar 2020, at 02:00, niftybunny >> wrote: >> >> My bad. Never seen this before. I there a good reason for the accept >> 133.0.0.0/8:80 ? >> >>> On 26. Mar 2020, at 15:06, ger...@bulger.co.uk wrote: >>> >>> "btw, you need to have at least port 80 and 443 … port 80 is

Re: [tor-relays] BadExit

> On 27 Mar 2020, at 20:42, teor wrote: > >>> On 26. Mar 2020, at 15:06, ger...@bulger.co.uk wrote: >>> >>> "btw, you need to have at least port 80 and 443 … port 80 is missing …" >>> >>> It there. But to a /8 area IPV4, all IPv6 >>> > The Exit flag only request one IPv4 /8 : >

Re: [tor-relays] BadExit

Hi, > On 27 Mar 2020, at 02:00, niftybunny > wrote: > > My bad. Never seen this before. I there a good reason for the accept > 133.0.0.0/8:80 ? > >> On 26. Mar 2020, at 15:06, ger...@bulger.co.uk wrote: >> >> "btw, you need to have at least port 80 and 443 … port 80 is missing …" >> >> It

Re: [tor-relays] BadExit

> -Original Message- > From: tor-relays On Behalf Of > niftybunny > Sent: 26 March 2020 12:49 > To: tor-relays@lists.torproject.org > Subject: Re: [tor-relays] BadExit > > btw, you need to have at least port 80 and 443 … port 80 is missing … > > Cheers, >

Re: [tor-relays] BadExit

ting seems to be exiting OK, but badexit tag still there. Gerry -Original Message- From: tor-relays On Behalf Of niftybunny Sent: 26 March 2020 12:49 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] BadExit btw, you need to have at least port 80 and 443 … port 80 is missing

Re: [tor-relays] BadExit

020 18:21 > To: tor-relays@lists.torproject.org > Subject: Re: [tor-relays] BadExit > > Hi! > > ger...@bulger.co.uk: >> Oh the shame! Never had that tag on my exit before. > > Sorry to hear. :( > >> >> >> I assume it was due to a bad boy

Re: [tor-relays] BadExit

: tor-relays On Behalf Of Georg Koppen Sent: 24 March 2020 18:21 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] BadExit Hi! ger...@bulger.co.uk: > Oh the shame! Never had that tag on my exit before. Sorry to hear. :( > > > I assume it was due to a bad boy att

[tor-relays] BadExit

Oh the shame! Never had that tag on my exit before. I assume it was due to a bad boy attacking an IP, pointed out by my ISP, and the ISP put my server "under mitigation".I assume some filtering, which of course would have looked bad to TOR users. I did not spot the ISP's email for 30

Re: [tor-relays] BadExit

Hi! ger...@bulger.co.uk: > Oh the shame! Never had that tag on my exit before. Sorry to hear. :( > > > I assume it was due to a bad boy attacking an IP, pointed out by my ISP, and > the ISP put my server "under mitigation".I assume some filtering, which > of course would have looked

Re: [tor-relays] BadExit why?

> Thank you for the answer. I try to get a new IP from the Trabia > support. that is not necessary if you can send your IP and wait for the directory authorities to update their config. Otherwise you might run into the same problem with the next IP address at that network. signature.asc

Re: [tor-relays] BadExit why?

Thank you for the answer. I try to get a new IP from the Trabia support. Olaf Am 12.02.19 um 21:51 schrieb David Goulet: > On 12 Feb (21:35:29), Olaf Grimm wrote: >>  inet 178.175.148.15 > Thanks Olaf! > > That IP was flagged as rewritting bitcoin addresses on Jan 21st, 2019. > > It appears

Re: [tor-relays] BadExit why?

Hi Olaf, Hydra10 is evidently no longer running so we can't tell you why it got the flag. Your other Hydra* relays aren't flagged that way so I wonder how Hydra10 differs. https://metrics.torproject.org/rs.html#search/Hydra On Tue, Feb 12, 2019 at 12:30 PM Olaf Grimm wrote: > > Hello ! > > I

Re: [tor-relays] BadExit why?

On 12 Feb (21:30:10), Olaf Grimm wrote: > Hello ! > > I provisioning a new exit since two hours. It is a totally new relay in > a VM. My other relays at the same provider are ok. Why I see "BadExit" > in Nyx??? Now my first bad experience with my 11 relays... > > fingerprint:

[tor-relays] BadExit why?

Hello ! I provisioning a new exit since two hours. It is a totally new relay in a VM. My other relays at the same provider are ok. Why I see "BadExit" in Nyx??? Now my first bad experience with my 11 relays... fingerprint: CCDC4A28392C7448A34E98DF872213BC16DB27CD Nickname Hydra10 At all exits I

Re: [tor-relays] badexit 29378422C99074D06331D5700E47451610B0D20D

Hi, I've cc'd bad-relays with this report. Please send reports of bad relays to bad-rel...@lists.torproject.org. > On 30 Jul 2017, at 02:56, eric gisse wrote: > > it looks like i've found an exit node mitm-ing ssh, or at least giving > it a shot. > >

[tor-relays] badexit 29378422C99074D06331D5700E47451610B0D20D

it looks like i've found an exit node mitm-ing ssh, or at least giving it a shot. https://atlas.torproject.org/#details/29378422C99074D06331D5700E47451610B0D20 that exit policy looks more like a wishlist than anything else, at this point. notice all 3 sites have different clear wire ssh keys

[tor-relays] badexit 03F84EA2E09CF427A519C65479DC0BF0D72886A6

router Tansam 79.143.87.234 443 0 0 03F84EA2E09CF427A519C65479DC0BF0D72886A6 Appears to be having trouble with, or is doing something with, http versions of https en.wikipedia.org articles. They're either blank or stripped of framework. ___ tor-relays

Re: [tor-relays] badexit D9B6E8F3DC60095F25252A1986E90932454C24D3

I also got certificate warnings when opening torbrowser. Vidalia told me I'm using this exit as well. It hasn't got the badexit flag yet. How long does it usually take for the dirauth operators to agree on that / deploy? I also had in mind that there was a exit relay scanner (from Mike?) that

Re: [tor-relays] badexit D9B6E8F3DC60095F25252A1986E90932454C24D3

On Sun, Jul 13, 2014 at 11:34:21AM +, Nusenu wrote: It hasn't got the badexit flag yet. The relay operator wasn't aware of the problem and said he would look into it on Monday. How long does it usually take for the dirauth operators to agree on that / deploy? It can range from one hour

[tor-relays] badexit D9B6E8F3DC60095F25252A1986E90932454C24D3

Breaks TLS on check.torproject.org, etc. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] badexit D9B6E8F3DC60095F25252A1986E90932454C24D3

On Sat, Jul 12, 2014 at 02:27:53PM -0400, grarpamp wrote: Breaks TLS on check.torproject.org, etc. Confirmed, thanks. Seems to be the relay's ISP. I contacted the operator and hopefully she/he will be able to fix it. Cheers, Philipp ___ tor-relays