Re: [tor-talk] Ongoing client problem

[Jacki M]

It is not a good idea to be on such a old version of OS X “security exploits 
that have been fixed in newer versions", my advice is to update to macOS 10.13 
(17A405) or the latest version and try to see if tor works then.

> On Oct 29, 2017, at 2:43 PM, Geoff Down  wrote:
> 
> 
> On Sun, Oct 29, 2017, at 06:59 PM, Roger Dingledine wrote:
>> On Sun, Oct 29, 2017 at 06:48:00PM +, George wrote:
>>> The route to determining the issue probably comes down to this
>>> error:> >
>>> Oct 29 12:50:06.000 [info] onion_skin_ntor_client_handshake():
>>> Invalid> > result from curve25519 handshake: 4
>> 
>> Right. That message comes when you tried to do a circuit-level
>> handshake> with a relay, but you were using the wrong onion key for it.
>> 
>>> ... but let me take a poke and ask if your time is synchronized?
>> 
>> A fine question. My first guess is that somehow your Tor client
>> is trying> to build circuits using obsolete directory information.
>> 
>> Another more distant option is that you (or your platform) have hacked> 
>> together your own curve25519 implementation and it's not working right> for 
>> you.
>> 
>> --Roger
>> 
> Thanks both for responding. It's OSX10.4, the clock is synchronized via
> NTP, openssl is the latest port, and the problem affects any application
> using Tor - curl, polipo, tsocks and even tor-resolve time-out in a
> similar way.I have seen messages to the effect of 'client request when we no 
> longer
> have a valid consensus' and also 'very long circuit build time -
> assuming clock jump'. I think it more likely that Tor is freezing ( I
> see no increase in cpu time at all with 'ps') sometimes and therefore
> the clock appears to jump when it unfreezes. Is that a possibility?
> -- 
> tor-talk mailing list - tor-talk@lists.torproject.org
> To unsubscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Re: [tor-talk] Ongoing client problem

[Geoff Down]

On Sun, Oct 29, 2017, at 06:59 PM, Roger Dingledine wrote:
> On Sun, Oct 29, 2017 at 06:48:00PM +, George wrote:
> > The route to determining the issue probably comes down to this
> > error:> >
> > Oct 29 12:50:06.000 [info] onion_skin_ntor_client_handshake():
> > Invalid> > result from curve25519 handshake: 4
>
> Right. That message comes when you tried to do a circuit-level
> handshake> with a relay, but you were using the wrong onion key for it.
>
> > ... but let me take a poke and ask if your time is synchronized?
>
> A fine question. My first guess is that somehow your Tor client
> is trying> to build circuits using obsolete directory information.
>
> Another more distant option is that you (or your platform) have hacked> 
> together your own curve25519 implementation and it's not working right> for 
> you.
>
> --Roger
>
Thanks both for responding. It's OSX10.4, the clock is synchronized via
NTP, openssl is the latest port, and the problem affects any application
using Tor - curl, polipo, tsocks and even tor-resolve time-out in a
similar way.I have seen messages to the effect of 'client request when we no 
longer
have a valid consensus' and also 'very long circuit build time -
assuming clock jump'. I think it more likely that Tor is freezing ( I
see no increase in cpu time at all with 'ps') sometimes and therefore
the clock appears to jump when it unfreezes. Is that a possibility?
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Re: [tor-talk] Ongoing client problem

[Roger Dingledine]

On Sun, Oct 29, 2017 at 06:48:00PM +, George wrote:
> The route to determining the issue probably comes down to this error:
> 
> Oct 29 12:50:06.000 [info] onion_skin_ntor_client_handshake(): Invalid
> result from curve25519 handshake: 4

Right. That message comes when you tried to do a circuit-level handshake
with a relay, but you were using the wrong onion key for it.

> ... but let me take a poke and ask if your time is synchronized?

A fine question. My first guess is that somehow your Tor client is trying
to build circuits using obsolete directory information.

Another more distant option is that you (or your platform) have hacked
together your own curve25519 implementation and it's not working right
for you.

--Roger

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Re: [tor-talk] Ongoing client problem

[George]

Geoff Down:
> Sadly not available for my OS.
> 

Troubleshooting a combination of Tor from source + Vidalia (still
maintained?) + some browser on an unknown OS is difficult.

What is your OS and browser?

The route to determining the issue probably comes down to this error:

Oct 29 12:50:06.000 [info] onion_skin_ntor_client_handshake(): Invalid
result from curve25519 handshake: 4

... but let me take a poke and ask if your time is synchronized?

g
-- 


34A6 0A1F F8EF B465 866F F0C5 5D92 1FD1 ECF6 1682
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Re: [tor-talk] Ongoing client problem

[Jacki M]

What OS are you using?

> On Oct 29, 2017, at 11:43 AM, Geoff Down  wrote:
> 
> Sadly not available for my OS.
> 
> 
> On Sun, Oct 29, 2017, at 06:39 PM, Jacki M wrote:
>> Just use the TorBrowser Bundle and see if that fixes your issue.
>> 
> -- 
> tor-talk mailing list - tor-talk@lists.torproject.org
> To unsubscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Re: [tor-talk] Ongoing client problem

[Geoff Down]

Sadly not available for my OS.


On Sun, Oct 29, 2017, at 06:39 PM, Jacki M wrote:
> Just use the TorBrowser Bundle and see if that fixes your issue.
>
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Re: [tor-talk] Ongoing client problem

[Jacki M]

Just use the TorBrowser Bundle and see if that fixes your issue.

> On Oct 29, 2017, at 6:07 AM, Geoff Down  wrote:
> 
> Hello all,
> my current experience of Tor is very frustrating in that it generally
> won't work for any length of time without changing identity, sending a
> SIGHUP or completely restarting. Since I've tried various versions
> (built from source), I assume the problem is with some other OS
> component or dependency. The following unedited log extract typifies the
> problem: identical curl requests to the Socks port which timed out
> 'Failed to receive SOCKS5 connect request ack' when the URL is fine over
> clearnet. Using Vidalia to look at circuits, I often see many in the
> 'Building' state permanently, or even just 'Path empty', but completed
> circuits will often not work either.
> Using 'new identity' usually produces a complete working circuit after a
> few attempts.
> More logs available if anyone wants them - but since this probably isn't
> a Tor bug, I won't open a Trac ticket.
> Regards,
> Geoff
> 
> Oct 29 11:50:02.000 [info] connection_handle_listener_read(): New SOCKS
> connection opened from 127.0.0.1.
> Oct 29 11:50:02.000 [info] connection_edge_process_inbuf(): data from
> edge while in 'waiting for circuit' state. Leaving it on buffer.
> Oct 29 11:50:02.000 [info] choose_good_exit_server_general(): Found 631
> servers that might support 1/1 pending connections.
> Oct 29 11:50:02.000 [info] choose_good_exit_server_general(): Chose exit
> server '$78E2BE744A53631B4AAB781468E94C52AB73968B~bynumlawtor at
> 104.200.20.46'
> Oct 29 11:50:03.000 [info] circuit_send_next_onion_skin(): First hop:
> finished sending CREATE cell to '$yyy~xxx at 51.15.61.46'
> Oct 29 11:50:03.000 [info] circuit_finish_handshake(): Finished building
> circuit hop:
> Oct 29 11:50:03.000 [info] exit circ (length 3, last hop bynumlawtor):
> $yyy(open) $2D5FE8689855F9F36B414B908B807981F18F2683(closed)
> $78E2BE744A53631B4AAB781468E94C52AB73968B(closed)
> Oct 29 11:50:03.000 [info] circuit_send_next_onion_skin(): Sending
> extend relay cell.
> Oct 29 11:50:12.000 [info] connection_edge_process_inbuf(): data from
> edge while in 'waiting for circuit' state. Leaving it on buffer.
> Oct 29 11:50:12.000 [info] connection_edge_reached_eof(): conn (fd 13)
> reached eof. Closing.
> Oct 29 12:50:03.000 [info] connection_handle_listener_read(): New SOCKS
> connection opened from 127.0.0.1.
> Oct 29 12:50:03.000 [info] connection_edge_process_inbuf(): data from
> edge while in 'waiting for circuit' state. Leaving it on buffer.
> Oct 29 12:50:05.000 [info] choose_good_exit_server_general(): Found 631
> servers that might support 1/1 pending connections.
> Oct 29 12:50:05.000 [info] choose_good_exit_server_general(): Chose exit
> server '$A571351082A9E04F14A0A3DF27E0637231D57B84~torfa at
> 79.172.193.32'
> Oct 29 12:50:05.000 [info] circuit_send_next_onion_skin(): First hop:
> finished sending CREATE cell to '$yyy~xxx at 51.15.61.46'
> Oct 29 12:50:05.000 [info] circuit_finish_handshake(): Finished building
> circuit hop:
> Oct 29 12:50:05.000 [info] exit circ (length 3, last hop torfa):
> $yyy(open) $823701D5C4C5D72C3FF533113F25A1922DED6303(closed)
> $A571351082A9E04F14A0A3DF27E0637231D57B84(closed)
> Oct 29 12:50:05.000 [info] circuit_send_next_onion_skin(): Sending
> extend relay cell.
> Oct 29 12:50:06.000 [info] entry_guard_inc_circ_attempt_count(): Got
> success count 230.375000/279.125000 for guard xxx ($yyy)
> Oct 29 12:50:06.000 [info] circuit_finish_handshake(): Finished building
> circuit hop:
> Oct 29 12:50:06.000 [info] exit circ (length 3, last hop torfa):
> $yyy(open) $823701D5C4C5D72C3FF533113F25A1922DED6303(open)
> $A571351082A9E04F14A0A3DF27E0637231D57B84(closed)
> Oct 29 12:50:06.000 [info] circuit_send_next_onion_skin(): Sending
> extend relay cell.
> Oct 29 12:50:06.000 [info] onion_skin_ntor_client_handshake(): Invalid
> result from curve25519 handshake: 4
> Oct 29 12:50:12.000 [info] connection_edge_process_inbuf(): data from
> edge while in 'waiting for circuit' state. Leaving it on buffer.
> Oct 29 12:50:12.000 [info] connection_edge_reached_eof(): conn (fd 13)
> reached eof. Closing.
> -- 
> tor-talk mailing list - tor-talk@lists.torproject.org
> To unsubscribe or change other settings go to
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk