Delivery-Date: Wed, 06 May 2015 08:56:04 -0400
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.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD 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 9C7B21E0AA9
	for <archiver@seul.org>; Wed,  6 May 2015 08:56:02 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 27B8E352C9;
	Wed,  6 May 2015 12:55:58 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D6250351DB
 for <tor-talk@lists.torproject.org>; Wed,  6 May 2015 12:55:54 +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 LagE7xiVnlTK for <tor-talk@lists.torproject.org>;
 Wed,  6 May 2015 12:55:54 +0000 (UTC)
Received: from smtp.ini-tech.com (albert.ini-tech.com [192.99.35.19])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id BAC3A351D3
 for <tor-talk@lists.torproject.org>; Wed,  6 May 2015 12:55:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp.ini-tech.com (Postfix) with ESMTP id 643A2A0C59
 for <tor-talk@lists.torproject.org>; Wed,  6 May 2015 12:57:27 +0000 (UTC)
Received: from smtp.ini-tech.com ([127.0.0.1])
 by localhost (smtp.ini-tech.com [127.0.0.1]) (amavisd-new, port 10032)
 with ESMTP id ub046pUXADT8 for <tor-talk@lists.torproject.org>;
 Wed,  6 May 2015 12:57:24 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp.ini-tech.com (Postfix) with ESMTP id 543E4A0C5C
 for <tor-talk@lists.torproject.org>; Wed,  6 May 2015 12:57:24 +0000 (UTC)
Received: from smtp.ini-tech.com ([127.0.0.1])
 by localhost (smtp.ini-tech.com [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id xxEpeLFm5_xA for <tor-talk@lists.torproject.org>;
 Wed,  6 May 2015 12:57:24 +0000 (UTC)
Received: from raoul (unknown [96.127.212.51])
 by smtp.ini-tech.com (Postfix) with ESMTPSA id 2994FA0C59
 for <tor-talk@lists.torproject.org>; Wed,  6 May 2015 12:57:24 +0000 (UTC)
Date: Wed, 6 May 2015 08:55:48 -0400
From: David Goulet <dgoulet@ev0ke.net>
To: tor-talk@lists.torproject.org
Message-ID: <20150506125548.GA6791@raoul>
References: <mailman.81.1430890508.2803.tor-talk@lists.torproject.org>
 <A27A4468-8981-4370-85AC-6F0A75881BF4@gmail.com>
MIME-Version: 1.0
In-Reply-To: <A27A4468-8981-4370-85AC-6F0A75881BF4@gmail.com>
Subject: Re: [tor-talk] 100-Foot Overview on Tor
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: multipart/mixed; boundary="===============2946341613322329378=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


--===============2946341613322329378==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5"
Content-Disposition: inline


--bg08WKrSYDhXBjb5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 06 May (19:28:38), teor wrote:
> >=20
> > Date: Tue, 5 May 2015 18:49:39 -0500
> > From: Tom Ritter <tom@ritter.vg>
> >=20
> > On 5 May 2015 at 07:53, Fabian Keil <freebsd-listen@fabiankeil.de> wrot=
e:
> >> Great.
> >>=20
> >> A couple of comments (about v1.3):
> >=20
> > Thanks! I made the changes and put up a 1.4
> >=20
> >> Page 141 and 142 seem to suggest that parsing strings is more
> >> likely to be vulnerable than parsing binary data. Is that intended?
> >=20
> > No but mostly yes. It's more a surprise factor: when I tell people tor
> > uses HTTP to upload and download things, they're not surprised - when
> > I tell them it has its own HTTP server implementation that does all
> > the parsing of the requests, they're much more surprised.  I'm not
> > saying tor's code is insecure (I put up a $bounty inside my company
> > with my own money to anyone who finds a bug in it actually) - but
> > implementing your own HTTP server is not a recommended action. :)
> >=20
> >> Is the source of the PDF available under a free license?
> >>=20
> >> I'm currently preparing a (German) presentation about location
> >> hidden block storage and could reuse the HS-related parts:
> >> http://chaos.cologne/Fahrplan/events/6653.html
> >=20
> > It's (now) http://creativecommons.org/licenses/by-sa/4.0/
> >=20
> > As far as the sources.... well, I made it in keynote. Yes, I know I'm
> > a bad person. I can export it as powerpoint, html, images, or pdf and
> > send you any one of those five. (Or all of them.)
>=20
> Hi Tom,
>=20
> Some further feedback:
>=20
> Page 20:
> Can you explain why you say that consensuses are valid for 24 hours, and =
not 3 hours?

Indeed, according to dir-spec.txt, see section "1.4 Voting timeline",
there is an explanation. The current tor code actually randomize some of
those values to be in a specific range that is not more than 3 hours
(iirc).

>=20
> Page 113:
> I think there are 3 relays between the client and introduction point, not=
 2.
> In new_route_len(), each circuit with an endpoint chosen by another relay=
 gets an extra hop, and the hidden service chooses the introduction point, =
not the client.
>=20
> I could be wrong about this - the path code has a few special cases that =
I haven't quite got my head around.

Yes you are right. Not only that but if the first introduction point
fails (client side), the circuit is re-extended to the second intro
point and so on until it works or the the maximum limit of 7 hops is
reached.

That's maybe a bit too deep to explain in the slides so I guess 4 hops
Client <-> Intro is good enough. :)

Tom, those slides are great! Impressive job! Thanks for this.

David

>=20
> teor
>=20
> teor2345 at gmail dot com
> pgp 0xABFED1AC
> https://gist.github.com/teor2345/d033b8ce0a99adbc89c5
>=20
> teor at blah dot im
> OTR D5BE4EC2 255D7585 F3874930 DB130265 7C9EBBC7
>=20



> --=20
> 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


--bg08WKrSYDhXBjb5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQF8BAEBCABmBQJVSg9UXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCNzQ0MTdFRERGMjJBQzlGOUU5MEY0OTE0
MkU4NkEyQTExRjQ4RDM2AAoJEELoaioR9I02KKsH/RldL5TO5208nxhFHCvYJ20A
ULf+dYrFQRPcP41+SleIS3R+ANucWdn2geti/MlB6uJdP7g5OsAxoSG/jQSrq3sk
EqSDj6dGaW3i6j4EXli2QTNm/uUTO+QA+ikaFNpqdgVM7zNIA5cAKLqC8J+1jimT
cCeIb56qnsThi3alkreNXdBlkKS9Nb+u+XvslWX1n/1RM/AU5UtJLoleU5kdePoM
XOYHG1ZtNi5gquQCgjMpfQjeH6TSnCnOBRhUAyg+s5rkKSkNB37AmhquXvQxzfXp
7dMRmp6xZoz3Lk87ZSBgKkwlwJRrzIzwy79ymYPgA6ZHBVJnSdo/DSvAXH6H7cE=
=kvZ2
-----END PGP SIGNATURE-----

--bg08WKrSYDhXBjb5--

--===============2946341613322329378==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
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

--===============2946341613322329378==--

