[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor fails to build connections after FreeBSD security update
- To: tor-relays@xxxxxxxxxxxxxx
- Subject: Re: Tor fails to build connections after FreeBSD security update
- From: Hans Schnehl <torvallenator@xxxxxxxxx>
- Date: Sat, 5 Dec 2009 19:36:13 +0100
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: tor-relays-outgoing@xxxxxxxx
- Delivered-to: tor-relays@xxxxxxxx
- Delivery-date: Sat, 05 Dec 2009 13:36:38 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=Dc7qoDo44XGdYXpUrMOYkdwi/AdB07KoOnZwjN10Zig=; b=Ts9tR/aOtBNKgV9D33h8ADAcrjc3t8cdAm1pu5xnPmYVQhXY+Wx1jDpXH7cvviq9Xt G30Dq79hYMTAKhyOba65po7IxxHGAcuW8Wt/Pi42Cfui5Anw+HZ1QnBBCClLl4OGDA6r WM/3uR5virF5cNmXGknZFTuj9n6NTsv20uSJo=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=QB73+ZvlXQ3AmRobCbrPnCT26JMD03paxAxYe1y8Edhr5cGYVGzVFaOhiuEhvJ1uZB EBdX2P16Bat8z5rll4JJyQD4497dwhE/YD7QcFp+ezDNaVMsfbEjkEUy9b198FtDDMR9 rw2h+8sGjLT/eycSKdgQ2BCY4C3+cRUDaqgio=
- In-reply-to: <4B1A8CC5.4000602@xxxxxxxxxxxxxx>
- References: <20091205145419.GA15687@tabulara> <4B1A8CC5.4000602@xxxxxxxxxxxxxx>
- Reply-to: tor-relays@xxxxxxxxxxxxxx
- Sender: owner-tor-relays@xxxxxxxxxxxxxx
- User-agent: Mutt/1.5.19 (2009-01-05)
On Sat, Dec 05, 2009 at 11:39:33AM -0500, Andrew Lewman wrote:
>
> Tor initiates a ssl renegotiate at the start of a circuit, the latest
> openssl breaks tor. The fixes for this are currently in -alpha only.
> The 0.2.1.21-dev in git also contains the fix. We're testing
> 0.2.2.6-alpha right now,
> https://blog.torproject.org/blog/tor-0226-alpha-released. Please try
> 0.2.2.6-alpha and let us know if it works.
Tor version 0.2.2.6-alpha (git-1ee580407ccb9130) was where this started.
That's the current from the official download page now and the one in
the FreBSD ports.
Tried Tor version 0.2.2.6-alpha-dev (git-4afdb79051f7b1ca) from a minute
ago or so, fails with OpenSSL 0.9.8e, runs "sort of" with 0.9.8.l but
still gives the following:
[snip)
Dec 05 18:05:22.693 [info] connection_edge_process_inbuf(): data from edge
while in 'waiting for circuit' state. Leaving it on buffer.
Dec 05 18:05:22.693 [info] connection_edge_process_inbuf(): data from edge
while in 'waiting for circuit' state. Leaving it on buffer.
Dec 05 18:05:23.295 [warn] TLS error: unexpected close while renegotiating
(SSL_ST_OK)
Dec 05 18:05:23.295 [info] connection_tls_continue_handshake(): tls error
[unexpected close]. breaking connection.
Dec 05 18:05:23.295 [info] circuit_n_conn_done(): or_conn failed. Closing
circ.
[snip]
>
> If 0.2.2.6-alpha is shown to work well, then we'll release
> 0.2.1.21-stable soon.
>
Well, not really...
> Thanks for running a relay!
You're welcome !
Was there a general change in handling StrictEntryNodes, as this does not
work in either combination ?
P.S.: Client with 0.2.2.6-alpha-dev (git-4afdb79051f7b1ca) does NOT run,
see:
[snip]
un (up never-contacted),humain (up never-contacted),Strobe (up
never-contacted),moi (up never-contacted),ThinkPenguin (down
never-contacted),Unnamed (up never-contacted),Unnamed (up
never-contacted),wikileaks (up never-contacted),dametenshi (up
never-contacted)
Dec 05 18:30:09.680 [info] circuit_expire_building(): Abandoning circ 0
(state 2:connecting to server, purpose 5)
Dec 05 18:30:09.680 [info] exit circ (length 3, exit gpfTOR6):
$85E9BAF52F2145FBE744C70B3C5CFB04CB6DF6DD(closed) GEO(closed)
gpfTOR6(closed)
Dec 05 18:30:09.680 [info] circuit_build_failed(): Our circuit died before
the first hop with no connection
Dec 05 18:30:09.680 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:10.702 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:11.724 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:12.742 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:13.763 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:14.785 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:15.808 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:16.830 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:17.853 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:18.875 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:19.897 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:20.919 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:21.942 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:22.964 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:23.986 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit circ.
Dec 05 18:30:25.008 [info] circuit_predict_and_launch_new(): Have 2 clean
circs (0 internal), need another exit
[snip]
:(