Re: [tor-relays] bad exit flag reason (128814837EC27)

2017-09-24 Thread nusenu 
>> [1] is not maintained since a long time.
>> I'm curious what the reason for assigning the badexit flag to [2]
>> was. If you know anything about it and can share something, that would
>> be great.
>>
>> [2] https://atlas.torproject.org/#search/flag:badexit
>>
>> 37.221.171.234 75FCEA0BE7A2A472669352A1F0F2E59F99C6A3AA
>> 37.221.171.237 128814837EC27F20D76EBDDB2CB3AB70258F0BA8
> 
> It was badexited in October 2015, with the reason "rewrite HTTP requests
> to port 8123".
> 
> That's the polipo port, so I wonder if they were running some sort of
> polipo + broken iptables setup.
> 
> There were a pile of exit relays around that address, all messing with
> exit traffic on that port, and most of them have disappeared since then.

Thank you for that info.

I see the majority of dirauths removed the badexit flag now for relay:
128814837EC27F20D76EBDDB2CB3AB70258F0BA8

Was that because it was a long time ago or because it is no longer an
exit (reject *:* exit policy)?

https://lists.torproject.org/pipermail/tor-consensus-health/2017-September/008151.html

-- 
https://mastodon.social/@nusenu
https://twitter.com/nusenu_



signature.asc
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] bad exit flag reason

2017-09-23 Thread Roger Dingledine 
On Sat, Sep 23, 2017 at 10:32:00PM +, nusenu wrote:
> Hi,
> 
> [1] is not maintained since a long time.
> I'm curious what the reason for assigning the badexit flag to [2]
> was. If you know anything about it and can share something, that would
> be great.
> 
> [2] https://atlas.torproject.org/#search/flag:badexit
> 
> 37.221.171.234 75FCEA0BE7A2A472669352A1F0F2E59F99C6A3AA
> 37.221.171.237 128814837EC27F20D76EBDDB2CB3AB70258F0BA8

It was badexited in October 2015, with the reason "rewrite HTTP requests
to port 8123".

That's the polipo port, so I wonder if they were running some sort of
polipo + broken iptables setup.

There were a pile of exit relays around that address, all messing with
exit traffic on that port, and most of them have disappeared since then.

--Roger

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

Re: [tor-relays] bad exit flag reason

2017-09-23 Thread teor 

> On 24 Sep 2017, at 08:32, nusenu  wrote:
> 
> Hi,
> 
> [1] is not maintained since a long time.
> I'm curious what the reason for assigning the badexit flag to [2]
> was. If you know anything about it and can share something, that would
> be great.

A better email address for this question is bad-relays@

https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays#MyrelayswasgiventheBadExitflag.Whatsup

> [2] https://atlas.torproject.org/#search/flag:badexit
> 
> 37.221.171.234 75FCEA0BE7A2A472669352A1F0F2E59F99C6A3AA
> 37.221.171.237 128814837EC27F20D76EBDDB2CB3AB70258F0BA8
> 
> [1] https://trac.torproject.org/projects/tor/wiki/doc/badRelays

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org






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

[tor-relays] bad exit flag reason

2017-09-23 Thread nusenu 
Hi,

[1] is not maintained since a long time.
I'm curious what the reason for assigning the badexit flag to [2]
was. If you know anything about it and can share something, that would
be great.

thanks,
nusenu


[2] https://atlas.torproject.org/#search/flag:badexit

37.221.171.234 75FCEA0BE7A2A472669352A1F0F2E59F99C6A3AA
37.221.171.237 128814837EC27F20D76EBDDB2CB3AB70258F0BA8

[1] https://trac.torproject.org/projects/tor/wiki/doc/badRelays

-- 
https://mastodon.social/@nusenu
https://twitter.com/nusenu_



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Bad exit

2012-09-17 Thread grarpamp 
Exit (one of these two I think, no guarantees):
109C56AC68DB55D16E79F832E19313E6C3E47363
67FD1D03F922975269F94EC7E4FD38C6D0E5E900 - torservers?

It's not occurring now via them, but whatever exit it
was generated these...

Error:
mail.google.com uses an invalid security certificate.
The certificate is only valid for the following names:
  *.mywebdav.de , mywebdav.de
(Error code: ssl_error_bad_cert_domain)

Erroneous public key presented:
aa 94 04 12 c4 32 2b c9 62 48 00 88 16 6f cd 8a
21 22 fe 6d 9d 51 63 6f 85 62 db 9c b5 3f e6 bf
1d 45 ca 51 57 3d 5f 83 97 73 b6 dd 99 86 d8 27
e5 07 71 94 cf d5 a4 92 a6 25 f8 06 fd 50 6c ad
70 2c 71 ca 66 38 1d 35 93 f1 c3 ff 52 6a 90 3d
54 fd 6f 69 34 9f 59 29 aa 05 59 91 95 33 53 8b
e6 b6 cf 65 dc 02 1a 31 57 d8 f4 11 70 f5 68 46
13 af c1 dc f0 b0 ce 43 b3 13 61 8a 18 00 84 32
2b 9a 9c aa 49 f3 fc b6 a1 d2 a9 d9 bd b4 53 a0
60 46 e7 e9 22 9d 23 08 5c 91 32 89 e7 85 4e ec
18 b7 d0 b3 6b 74 fa b4 f3 08 11 1f 1b e1 55 e9
7b 90 f4 64 93 08 a2 58 70 e0 c6 41 f9 f9 d0 9c
b1 3d e9 b6 ae b3 73 ac 11 d3 f6 91 9e 79 f2 b4
d7 7d 96 8a 83 30 b1 bf 40 6f 18 24 42 43 b7 b1
65 7e 3d 1f d2 47 e9 fb 2e 10 21 7c ce 20 a8 c3
35 f3 d8 91 d1 a6 a1 87 52 4b de 39 1e ec b9 4d
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Bad exit

2012-09-17 Thread Robert Ransom 
On 9/17/12, grarpamp grarp...@gmail.com wrote:
 Exit (one of these two I think, no guarantees):
 109C56AC68DB55D16E79F832E19313E6C3E47363
 67FD1D03F922975269F94EC7E4FD38C6D0E5E900 - torservers?

 It's not occurring now via them, but whatever exit it
 was generated these...

 Error:
 mail.google.com uses an invalid security certificate.
 The certificate is only valid for the following names:
   *.mywebdav.de , mywebdav.de
 (Error code: ssl_error_bad_cert_domain)

I saw this a few days ago.  Some exit node (I couldn't find out which)
had sent a bogus DNS response which my Tor client cached; the exit
nodes you list are probably innocent.


Robert Ransom
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Bad exit

2012-09-17 Thread Rejo Zenger 

On 17 sep. 2012, at 10:44, Runa A. Sandvik wrote:

 Yep, I was seeing the same thing a few minutes ago (I believe the exit
 was 109C56AC68DB55D16E79F832E19313E6C3E47363, but someone should test
 and confirm).


I cannot reproduce this issue. I have specified this exit node to be used as 
exit, verified based on IP-address and key. I was presented with a certificate 
I believe was valid.

-- 
Rejo Zenger r...@zenger.nl| GPG: 0x21DBEFD4
https://rejo.zenger.nl/
+31 (0) 6 39 64 27 38





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays