[email protected] wrote: > On Tue, Feb 16, 2010 at 01:22:42PM +0100, [email protected] wrote 3.6K > bytes in 65 lines about: > : [warn] TLS error: unexpected close while renegotiating > > This means your openssl disabled renegotiation. Which is odd because my > debian doesn't have this problem. > > When Tor starts up, there should be a log entry about openssl version, > what does yours say?
I don't find a log entry, but "dpkg -l openssl": ii openssl 0.9.8k-8 I've removed tor (aptitude remove tor, aptitude purge tor) I've commented out in /etc/apt/sources: deb http://deb.torproject.org/torproject.org testing main I've reinstalled the old packet (aptitude install tor) Now it seems to work fine, like before upgrade to v23 Terminal: serv:/etc/ssl# /etc/init.d/tor start Raising maximum number of filedescriptors (ulimit -n) to 32768. Starting tor daemon: tor... Feb 16 14:11:02.266 [notice] Tor v0.2.1.23. This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686) Feb 16 14:11:02.268 [notice] Choosing default nickname 'serv' Feb 16 14:11:02.271 [notice] Initialized libevent version 1.4.13-stable using method epoll. Good. Feb 16 14:11:02.271 [notice] Opening OR listener on 0.0.0.0:443 done. /var/log/tor/log: Feb 16 14:28:25.594 [notice] Tor 0.2.1.22 opening log file. Feb 16 14:28:25.598 [notice] Parsing GEOIP file. Feb 16 14:28:28.064 [notice] Your Tor server's identity key fingerprint is 'serv D5DC93D93777502464BF6F88562F36ED9FB57336' Feb 16 14:28:28.289 [notice] We're missing a certificate from authority with signing key 1FD9845C566C40EC0401B9857C98824CB6D4F747: launching request. Feb 16 14:28:28.289 [notice] We're missing a certificate from authority with signing key 42CF43879B4F1188CB428564EE1D319CE7C502B9: launching request. Feb 16 14:28:29.716 [notice] We now have enough directory information to build circuits. Feb 16 14:28:29.716 [notice] Bootstrapped 80%: Connecting to the Tor network. Feb 16 14:28:29.762 [notice] Bootstrapped 85%: Finishing handshake with first hop. Feb 16 14:28:29.844 [notice] Guessed our IP address as 212.185.231.158 (source: 137.56.163.117). Feb 16 14:28:30.115 [notice] Bootstrapped 90%: Establishing a Tor circuit. Feb 16 14:28:31.309 [notice] Tor has successfully opened a circuit. Looks like client functionality is working. Feb 16 14:28:31.309 [notice] Bootstrapped 100%: Done. Feb 16 14:28:31.309 [notice] Now checking whether ORPort 212.185.231.158:443 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) Feb 16 14:28:31.973 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. Feb 16 14:30:36.686 [notice] Performing bandwidth self-test...done. --------- Benn *********************************************************************** To unsubscribe, send an e-mail to [email protected] with unsubscribe or-talk in the body. http://archives.seul.org/or/talk/
