Date: Tue, 14 Jul 2015 10:05:48 -0600 From: jd1008 <jd1008@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Another tor question Message-ID: <55A5335C.9040907@gmail.com> In-Reply-To: <55A4FFF7.2020400@hiwaay.net> References: <55A4FFF7.2020400@hiwaay.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/14/2015 06:25 AM, William A. Mahaffey III wrote: > > > .... I am using tor with firefox to browse the web. Some sites seem to > detect & block this type of access. Sometimes, however, I seem to > slither through, usually 1st thing in the A.M. after my (cable-modem) > access has been offline all night & tor has dropped all of its > circuits (according to its log file). Is that in fact an accurate > analysis, i.e. I am browsing 'naked' until tor re-establishes circuits > ? System info: > > [root@kabini1, /etc, 7:31:25am] 551 % uname -a > FreeBSD kabini1.local 9.3-RELEASE-p13 FreeBSD 9.3-RELEASE-p13 #0: Tue > Apr 7 03:01:12 UTC 2015 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > [root@kabini1, /etc, 7:31:32am] 552 % > > tor-0.2.6.9, torsocks-2.0.0 > > From tor's log file: > > [root@kabini1, /etc, 7:26:59am] 440 % ( tail -20 /var/log/tor ; date ) > Jul 13 22:36:09.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:42:30.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:42:31.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:42:32.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:43:49.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:48:54.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:50:11.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:50:12.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:50:13.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:50:14.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:54:03.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:54:04.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:54:05.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:56:38.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:56:39.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:56:40.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:56:41.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 13 22:56:42.000 [warn] Failed to find node for hop 0 of our path. > Discarding this circuit. > Jul 14 01:58:43.000 [notice] Heartbeat: Tor's uptime is 1 day 18:00 > hours, with 0 circuits open. I've sent 27.67 MB and received 111.14 MB. > Jul 14 01:58:43.000 [notice] Average packaged cell fullness: 66.503%. > TLS write overhead: 9% > Tue Jul 14 07:30:39 MCDT 2015 > [root@kabini1, /etc, 7:30:39am] 440 % > > You found a chink in tor's armor :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55A5335C.9040907>