Re: [tor-relays] possible bad exit or bad circuit

[cmeclax-sazri <cmeclax-sazri@xxxxxxxxxxxxxxxx>]

On Sunday 24 July 2011 17:39:07 Fabian Keil wrote:
> I can reproduce it. Trying to access
> www.example.org.c20517b5cd15f21129f719eccc54fbca05ae7ee5.exit:
>
> Jul 24 23:08:35.065 [info] circuit_finish_handshake(): Finished building
> circuit hop: Jul 24 23:08:35.066 [info] exit circ (length 4, last hop
> tornodeca): [...](open) [...](open) [...](open)
> $C20517B5CD15F21129F719ECCC54FBCA05AE7EE5(open) Jul 24 23:08:35.066 [info]
> circuit_send_next_onion_skin(): circuit built! Jul 24 23:08:35.066 [info]
> exit circ (length 4): [...](open) [...](open) [...](open)
> $C20517B5CD15F21129F719ECCC54FBCA05AE7EE5(open) Jul 24 23:08:35.067 [info]
> connection_ap_handshake_send_begin(): Sending relay cell 0 to begin stream
> 4694. Jul 24 23:08:35.067 [info] connection_ap_handshake_send_begin():
> Address/port sent, ap socket 4, n_circ_id 7997 Jul 24 23:08:35.716 [info]
> connection_ap_process_end_not_open(): Edge got end (connection refused)
> before we're connected. Marking for close. Jul 24 23:08:35.716 [info] exit
> circ (length 4): [...](open) [...](open) [...](open)
> $C20517B5CD15F21129F719ECCC54FBCA05AE7EE5(open)
>
> No problems accessing
> www.torproject.org.c20517b5cd15f21129f719eccc54fbca05ae7ee5.exit:443

Okay, so it's not just me. I think that the other tornodeca should be flagged 
as BadExit too, even if it doesn't have the port blocked. Both have been up 
five days, both are named tornodeca, and both have the same invalid email 
address of the operator.
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays