Fwd: strange messages
?? -- Forwarded message -- From: M moeedsa...@gmail.com Date: Fri, Dec 3, 2010 at 9:11 AM Subject: strange messages To: or-talk@freehaven.net Hey again: i am getting this new message in forefox: Torbutton Sandbox evaluation failed. Date hooks not applied! Any clues?
Re: strange messages
Quoth M moeedsa...@gmail.com, on 2010-12-03 09:11:06 +: Hey again: i am getting this new message in forefox: Torbutton Sandbox evaluation failed. Date hooks not applied! Which version of Torbutton is this? Which version of Firefox, and which platform? My guess would be some extension incompatibility, but I don't know that much. --- Drake Wilson *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Stuck at 85%
Hi, Recently I got many this kind of error, and the connection is stuck at 85%, WHY? (Timestamp is scrubbed) [notice] Tor v0.2.2.19-alpha (git-e57cb6b9762a2f94). This is experimental softw re. Do not rely on it for strong anonymity. (Running on Windows Vista Service Pack 2 [workstation]) [notice] Initialized libevent version 1.4.14-stable using method win32. Good. [notice] Opening Socks listener on 127.0.0.1:9050 [notice] Parsing GEOIP file. [notice] OpenSSL OpenSSL 0.9.8p 16 Nov 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation [notice] new bridge descriptor 'Unnamed' (cached) [notice] We now have enough directory information to build circuits. [notice] Bootstrapped 80%: Connecting to the Tor network. [notice] Bootstrapped 85%: Finishing handshake with first hop. [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn) [notice] no known bridge descriptors running yet; stalling [notice] Our directory information is no longer up-to-date enough to build circ its: No live bridge descriptors. [notice] Application request when we haven't used client functionality lately. ptimistically trying known bridges again. [notice] We now have enough directory information to build circuits. [notice] Learned fingerprint 582223784EAFB561661F8C98EE0A062F62676EF5 for bridg 84.170.168.234:444 [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn) [notice] no known bridge descriptors running yet; stalling [notice] Our directory information is no longer up-to-date enough to build circ its: No live bridge descriptors. [notice] Application request when we haven't used client functionality lately. ptimistically trying known bridges again. [notice] We now have enough directory information to build circuits. [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 4; recommendation warn) [notice] no known bridge descriptors running yet; stalling [notice] Our directory information is no longer up-to-date enough to build circ its: No live bridge descriptors. [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit) [notice] Application request when we haven't used client functionality lately. ptimistically trying known bridges again. [notice] We now have enough directory information to build circuits. [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit) [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up (waiting for circuit) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 5; recommendation warn) [notice] no known bridge descriptors running yet; stalling [notice] Our directory information is no longer up-to-date enough to build circ its: No live bridge descriptors. [notice] Application request when we haven't used client functionality lately. ptimistically trying known bridges again. [notice] We now have enough directory information to build circuits. [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up (waiting for circuit) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 6; recommendation warn) [notice] no known bridge descriptors running yet; stalling [notice] Our directory information is no longer up-to-date enough to build circ its: No live bridge descriptors. [notice] Application request when we haven't used client functionality lately. ptimistically trying known bridges again. [notice] We now have enough directory information to build circuits. [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 7; recommendation warn) [notice] no known bridge descriptors running yet; stalling [notice] Our directory information is no longer up-to-date enough to build circ its: No live bridge descriptors. [notice] Application request when we haven't used client functionality lately. ptimistically trying known bridges again. [notice] We now have enough directory information to build circuits. [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up (waiting for circuit) [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up (waiting for circuit) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 8; recommendation warn) [notice] no known bridge descriptors running yet; stalling [notice] Our directory information is no longer up-to-date enough to build circ its: No live bridge descriptors.
Re: Stuck at 85%
On Sun, Dec 05, 2010 at 12:57:12AM +0800, Moses wrote: Recently I got many this kind of error, and the connection is stuck at 85%, WHY? [notice] new bridge descriptor 'Unnamed' (cached) [notice] We now have enough directory information to build circuits. [notice] Bootstrapped 80%: Connecting to the Tor network. [notice] Bootstrapped 85%: Finishing handshake with first hop. [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn) You have configured your Tor client to use one bridge, and you can't reach that bridge. (I can't reach it either -- it seems to be down.) So either find a bridge that works (is up and reachable for you), or stop using bridges and then you'll have more options for where to connect (should work everywhere but in China). --Roger *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: [notice] Circuit build measurement period of 218915ms is more than twice the maximum build time we have ever observed. Capping it to 152350ms.
On Sat, Dec 04, 2010 at 07:00:17AM +, Orionjur Tor-admin wrote: I have the above record in '/var/tor/log' on my exit-node. What it can mean?! Tor clients build circuits when they first start up, to estimate the average amount of time it takes to build a circuit. Once they have a good estimate, they abandon the slowest 20% of the circuits they make, since a circuit that takes a long time to build will probably be no fun to use. Your circuit build times appear to be really crummy. Your Tor has estimated that the 80% mark for you is 219 seconds. But in fact, the slowest circuit you've actually created took only 152 seconds. I believe this situation can occur when many of the circuits your Tor tries to make fail to get created at all. Are you rate limiting your exit node? Perhaps you should start. It seems like your network is really overloaded. --Roger *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Stuck at 85%
Hi, Thanks for reply. This is weird. Every new bridge I got just work for 2-5 minutes, and then becomes unreachable and the reconnection is stuck at 85%. Are bridges under attack? And after removed bridges, the things getting even worse, [notice] Tor v0.2.2.19-alpha (git-e57cb6b9762a2f94). This is experimental softwa [workstation]) [notice] Initialized libevent version 1.4.14-stable using method win32. Good. [notice] Opening Socks listener on 127.0.0.1:9050 [notice] Parsing GEOIP file. [notice] OpenSSL OpenSSL 0.9.8p 16 Nov 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation [notice] We now have enough directory information to build circuits. [notice] Bootstrapped 80%: Connecting to the Tor network. [notice] Bootstrapped 85%: Finishing handshake with first hop. [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 10; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 11; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 12; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 13; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 14; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 15; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 16; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 17; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 18; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 19; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 20; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 21; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 22; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 23; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 24; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 25; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 26; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 27; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 28; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 29; recommendation warn) [warn] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 30; recommendation warn) On Sun, Dec 5, 2010 at 2:41 AM, Roger Dingledine a...@mit.edu wrote: On Sun, Dec 05, 2010 at 12:57:12AM +0800, Moses wrote: Recently I got many this kind of error, and the connection is stuck at 85%, WHY? You have configured your Tor client to use one bridge, and you can't reach that bridge. (I can't reach it either -- it seems to be down.) So either find a bridge that works (is up and reachable for you), or stop using bridges and then you'll have more options for where to connect (should work everywhere but in China). --Roger *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Stuck at 85%
On Sun, Dec 05, 2010 at 03:06:14AM +0800, Moses wrote: Thanks for reply. This is weird. Every new bridge I got just work for 2-5 minutes, and then becomes unreachable and the reconnection is stuck at 85%. Are bridges under attack? And after removed bridges, the things getting even worse, What sort of firewall are you behind? --Roger *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: strange messages
Its the latest version of the Tor Browser for Mac. 1.0.4. On Sat, Dec 4, 2010 at 9:59 AM, Drake Wilson dr...@begriffli.ch wrote: Quoth M moeedsa...@gmail.com, on 2010-12-03 09:11:06 +: Hey again: i am getting this new message in forefox: Torbutton Sandbox evaluation failed. Date hooks not applied! Which version of Torbutton is this? Which version of Firefox, and which platform? My guess would be some extension incompatibility, but I don't know that much. --- Drake Wilson *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
Re: Arm Release 1.4.0
Hi all. I've checked in the resolver fixes (thank Fabian and Hans!) and a test tarball is available at: http://www.atagar.com/transfer/tmp/arm_bsdTest.tar.bz2 http://www.atagar.com/transfer/tmp/arm_bsdTest.tar.bz2.asc I've added both of the commands you mentioned as fallback resolvers. On Ubuntu procstat doesn't exist but sockstat does, so I've also added handling for its Linux version too: ata...@fenrir:~$ sockstat | egrep tor\s*3475.*ESTABLISHED atagar tor29672tcp4 192.168.0.3:36511scrubbed:9001 ESTABLISHED atagar tor29672tcp4 192.168.0.3:45906scrubbed:9001 ESTABLISHED atagar tor29672tcp4 192.168.0.3:60202scrubbed:4430 ESTABLISHED atagar tor29672tcp4 192.168.0.3:34600scrubbed:9001 ESTABLISHED ... For BSD I'm using the following commands: sockstat -4 | egrep 'process\s*pid' | grep -v '*:*' procstat -f 'pgrep process' | grep 'pid' | grep -v '0.0.0.0:0' The purpose of these greps is to only get established connections and to filter by the pid (in case there's multiple tor instances). To test please do the following: 1. Run arm at its debug runlevel (arm -e 1) 2. Arm defaults to the bsd resolvers if os.uname() matches FreeBSD. Please look for an entry like the following in your logs (it'll be near the start): 18:50:00 [ARM_INFO] Operating System: FreeBSD, Connection Resolvers: sockstat (bsd), procstat (bsd) if it doesn't match that then let me know what it says. 3. Go to arm's second page and press u to bring up the resolver options. Regardless of the OS detected it will have: * auto * netstat * ss * lsof * sockstat * sockstat (bsd) * procstat (bsd) 4. Select one of the bsd options. If it doesn't work then the results will be unchanged (ie, if options were already listed then they'll still be listed so don't trust that, please still check the following step for both). 5. Go back to the log. You'll see an entry like: 18:16:31 [ARM_DEBUG] system call: sockstat -4 | egrep 'tor\s*29672' | grep -v '*:*' (runtime: 0.03) Problems come in two flavors. Either the command resulted in an error, like: 18:15:40 [ARM_INFO] system call (failed): procstat -f 'pgrep tor' | grep '29672' | grep -v '0.0.0.0:0' (error: 'procstat' is unavailable) in which case please let me know what the error is, or it doesn't provide any results: 18:15:55 [ARM_INFO] No results found using: sockstat -4 | egrep 'tor\s*29672' | grep -v '*:*' in which case please try the command on its own and let me know how I screwed up the greps. after polling for lsof and a foreach loop, doesn't work ? ... would work ... especially if the system in question is doing little (or nothing) other than Tor ... Sorry, I'm not following. Why is a for-each loop necessary? Process and connection resolutions are the most costly lookups arm currently does. A netstat resolution, for instance, takes around 30-40 ms on my system and is performed every five seconds. Arm tries to be a lightweight application so running multiple system commands to do each lookup isn't really an option. That said, from the link you provided it looks like this isn't necessary. What arm currently attempts is: lsof -nPi | grep process\s*pid.*(ESTABLISHED) If FreeBSD has an equivalents for the flags (n = prevent dns lookups, P = show port numbers (not names), i = ip only) then please show me what its output looks like and I'd be happy to add it as another fallback resolver. What order should sockstat, procstat, and lsof be attempted in? Are any of them preferable due to jails over the others? However if lsof is the only way to do it right Nope, not necessary at all. But the more connection resolvers available for FreeBSD the more likely arm will be able to fall back to something that works. Cheers! -Damian *** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talkin the body. http://archives.seul.org/or/talk/
