Delivery-Date: Thu, 11 Dec 2014 02:18:49 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 4CF941E0FAC;
	Thu, 11 Dec 2014 02:18:48 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 8CEF031249;
	Thu, 11 Dec 2014 07:18:43 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 912B4311E1
 for <tor-talk@lists.torproject.org>; Thu, 11 Dec 2014 07:18:40 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 358liWQVJmJl for <tor-talk@lists.torproject.org>;
 Thu, 11 Dec 2014 07:18:40 +0000 (UTC)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com
 [IPv6:2a00:1450:400c:c05::235])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 409292F081
 for <tor-talk@lists.torproject.org>; Thu, 11 Dec 2014 07:18:40 +0000 (UTC)
Received: by mail-wi0-f181.google.com with SMTP id r20so7607362wiv.8
 for <tor-talk@lists.torproject.org>; Wed, 10 Dec 2014 23:18:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=iWuyJ9g85OC/p4TFz8zT7l406tLr0rPcuNP+biRi1JM=;
 b=Ox3tFABlP4M55DufMTZNSNMV3shS/hqasK84C8O3EcwXAIvbx+8RkMVUBsX2wZ43R8
 lO4dn9tBTxk2SquVyNKe1HAhL3buLuJy3Qase9wWrnx5R39SR0O8IX5GMXEwZrtxUYSG
 Y7E/nnkww8+HUq2UlAivxS0pDCqCdQE/J2ZKYSr5RKMK6RTnxJI/33Ep2xqMQ2JTad8w
 XZ79fjGT+bkoqj/9r3fx9+MKCt40Sbt1jLEXZohxPEAh3HnXezO6LihM6az/hMMgZLJl
 giuUAaoskbXI/LS2IALaG2US7kVFoRyZtp+2EXzO595hRXN9ZlEz9rbgGSS6KrYsrcgM
 /96Q==
MIME-Version: 1.0
X-Received: by 10.180.98.138 with SMTP id ei10mr13156296wib.32.1418282317412; 
 Wed, 10 Dec 2014 23:18:37 -0800 (PST)
Received: by 10.216.151.130 with HTTP; Wed, 10 Dec 2014 23:18:37 -0800 (PST)
In-Reply-To: <5cf56ef1f8f78a360d93f593f5fc7758@subvertising.org>
References: <22b9f013c8ef0f36b66963a8edc23f2c@subvertising.org>
 <54890250.7030600@riseup.net>
 <5cf56ef1f8f78a360d93f593f5fc7758@subvertising.org>
Date: Thu, 11 Dec 2014 02:18:37 -0500
Message-ID: <CAD2Ti2_bNmSF7duTii6Kg=PdJc4M8RC6tuYRsZC7ZtShyeOJ2A@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Tor network too fast
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Wed, Dec 10, 2014 at 9:51 PM, Sieme <sieme@hacari.com> wrote:
> How to check how many hops do a request?

Read control-spec.txt about how to connect to the controller and
issue commands to watch the circuits and streams.

https://gitweb.torproject.org/torspec.git/tree/

> But what's the default policy now? 3 hops?

It is 4 hops over 3 nodes to a clearnet destination.

> very little time (sometimes about 100ms).

That's 25ms average.

> How can be possible

It's very tight, but possible. Max avg RTT is ~1000ms.

> I tried to recompile Tor sources, but it's harder than changing a variable,

It is a single easy to find define. The default of three is the lowest
you can safely go, and it is also the optimum amount. Some
advocate four for some edge cases that aren't necessarily likely
to be used by an actual adversary. Once you find the variable name
you can search all the past threads about this. But until you've read
enough to really understand both Tor and your own security posture
to the point of being very well versed in both, turning random miracle
knobs in the source is not going to help you. Until then, stick to
what's in torrc.

> Or Tor is not secure by design as we think?

Tor is only good at what it's good at.
You can read all about that here:
https://www.torproject.org/docs/documentation.html.en
https://lists.torproject.org/pipermail/tor-talk/

> 100% of the sponsors come from our USA government

Forget about US govt funds, I bribed Tor with Swedish hookers
and Columbian blow. Much cheaper, works every time ;)
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

