From owner-freebsd-questions@freebsd.org Tue Jul 14 16:05:51 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9125D9A1667 for ; Tue, 14 Jul 2015 16:05:51 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5C813A8C for ; Tue, 14 Jul 2015 16:05:51 +0000 (UTC) (envelope-from jd1008@gmail.com) Received: by iggp10 with SMTP id p10so101736987igg.0 for ; Tue, 14 Jul 2015 09:05:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=fGUktXLv6Y5C1vX/wA39MA2TZoE673m2FZJM5HQjCYU=; b=COB54d4OS813+Seb/bjNBgYThO0ypY01hTy5GjrcQgx8vswhb0dTYvHk4iOpimQOZM JWVO9UOCFhdOIZr7BttxBLlJ6m9A4zXs5/5qJ3rKja+daSJ6v1hLcrUGdL444uJv29Mq iU0/mRtZSFO6TbPOune/nG2WCyLEHpo4hC6h3H5kXMwJN2zkXkU5cn9f+U7PBGioHlb0 7i9Z4wzcPpZK65YIHH46kcqvyFhyA7ZE32Dx2Vq2IyK3qP6BMLNkUo6XBVPIg2uLJRTR fNwX9Lff5ye68bGqcP6T8nP7A9rD0FOcaDmbAmg3sNk1nNRGXX1rO6RETG9woxT7MVYO ejNA== X-Received: by 10.50.40.42 with SMTP id u10mr15870210igk.71.1436889949959; Tue, 14 Jul 2015 09:05:49 -0700 (PDT) Received: from localhost.localdomain ([50.243.6.59]) by smtp.googlemail.com with ESMTPSA id o19sm8107135igs.18.2015.07.14.09.05.49 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Jul 2015 09:05:49 -0700 (PDT) Message-ID: <55A5335C.9040907@gmail.com> Date: Tue, 14 Jul 2015 10:05:48 -0600 From: jd1008 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Another tor question References: <55A4FFF7.2020400@hiwaay.net> In-Reply-To: <55A4FFF7.2020400@hiwaay.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 16:05:51 -0000 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 :)