[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #2001 [Tor Relay]: Reachability test for ORPort doesn't complete with --enable-bufferevents set
#2001: Reachability test for ORPort doesn't complete with --enable-bufferevents
set
-----------------------+----------------------------------------------------
Reporter: Sebastian | Owner: nickm
Type: defect | Status: accepted
Priority: normal | Milestone:
Component: Tor Relay | Version:
Keywords: | Parent:
-----------------------+----------------------------------------------------
Comment(by nickm):
So for some reason, now I can reproduce the OpenSSL 1.0.0a case.
Here is what I can tell: renegotiation works and the client successfully
calls connection_tls_finish_handshake. It completes, and the client sends
a VERSIONS cell. Go client!
The server gets to connection_or_handle_events_cb, and makes it to the
case commented as "improved handshake, but not a client". However, for
some reason it does NOT call connection_or_tls_renegotiated_cb! I am
guessing that the renegotiation has already finished by the time that we
reach connection_or_handle_events_cb on the server side!
Compare the client's
{{{
Oct 11 12:25:32.045 [debug] connection_tls_finish_handshake(): client
tls handshake (0x1e92d60) with [scrubbed] done. verifying.
}}}
with the server's
{{{
Oct 11 12:27:33.968 [debug] tor_tls_finish_handshake(): Completed V2
TLS handshake with client; waiting for renegotiation.
}}}
and take special note of the timestamps.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2001#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs