Is "gatereloaded" a Bad Exit?
Jan Weiher
jan at buksy.de
Sat Jan 29 20:37:41 UTC 2011
Am 29.01.2011 21:27, schrieb Gitano:
> On 2011-01-29 19:46, Jan Weiher wrote:
>
>> while scrolling through the tor status page (torstatus.blutmagie.de), I
>> stumpled upon the following node (the reason why it came to my eye was
>> the long uptime):
>>
>> gatereloaded 550C C972 4FA7 7C7F 9260 B939 89D2 2A70 654D 3B92
>>
>> This node looks suspicious to me, because there is no contact info given
>> and the exit policy allows only unencrypted traffic:
>>
>> reject 0.0.0.0/8:*
>> reject 169.254.0.0/16:*
>> reject 127.0.0.0/8:*
>> reject 192.168.0.0/16:*
>> reject 10.0.0.0/8:*
>> reject 172.16.0.0/12:*
>> reject 194.154.227.109:*
>> accept *:21
>> accept *:80
>> accept *:110
>> accept *:143
>> reject *:*
>>
>> Am I missing something? I'm wondering why the status page lists this
>> node as non-exit, because it clearly allows outgoing traffic on ports
>> 21,80,110 and 143?
>
> See:
> 'https://gitweb.torproject.org/arma/tor.git/blob_plain/03b9c2cb903cc59f83139039d963f1fdea99b83a:/doc/spec/dir-spec.txt'
>
> "Exit" -- A router is called an 'Exit' iff it allows exits to at
> least two of the ports 80, 443, and 6667 and allows exits to at
> least one /8 address space.
>
> Also: http://www.mail-archive.com/or-talk@freehaven.net/msg10275.html
this explains why the status page does not list the node as an exit
node. thanks.
But as far as I understand, the node does not get the "Exit"-Flag, but
it is still used for outgoing traffic on the accepted ports? So the
"main"-question is still unanswered.
best regars,
Jan
***********************************************************************
To unsubscribe, send an e-mail to majordomo at torproject.org with
unsubscribe or-talk in the body. http://archives.seul.org/or/talk/
More information about the tor-talk
mailing list