Delivery-Date: Tue, 05 May 2015 09:02:29 -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 0B7771E03B6
	for <archiver@seul.org>; Tue,  5 May 2015 09:02:27 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 430A834B22;
	Tue,  5 May 2015 13:02:22 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 021EA3389E
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 13:02:19 +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 5gWOQwpMOlWv for <tor-talk@lists.torproject.org>;
 Tue,  5 May 2015 13:02:18 +0000 (UTC)
Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de
 [80.67.31.97])
 (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 C3C1334973
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 13:02:18 +0000 (UTC)
X-Greylist: delayed 376 seconds by postgrey-1.34 at eugeni;
 Tue, 05 May 2015 13:02:18 UTC
Received: from [78.35.138.142] (helo=fabiankeil.de)
 by smtprelay05.ispgateway.de with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128)
 (Exim 4.84) (envelope-from <freebsd-listen@fabiankeil.de>)
 id 1YpcOC-0002XA-QP
 for tor-talk@lists.torproject.org; Tue, 05 May 2015 14:55:56 +0200
Date: Tue, 5 May 2015 14:53:54 +0200
From: Fabian Keil <freebsd-listen@fabiankeil.de>
To: tor-talk@lists.torproject.org
Message-ID: <16b261d3.1934b0ef@fabiankeil.de>
In-Reply-To: <CA+cU71kwWqGhtPaSbtQyOEtXXxTNUeJPULvnzvUCTC0oTxbu=A@mail.gmail.com>
References: <CA+cU71kwWqGhtPaSbtQyOEtXXxTNUeJPULvnzvUCTC0oTxbu=A@mail.gmail.com>
MIME-Version: 1.0
X-Df-Sender: Nzc1MDY3
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="===============5085488352927022060=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

--===============5085488352927022060==
Content-Type: multipart/signed; micalg=pgp-sha1;
 boundary="Sig_/ZNDR_qJYh3baf4EQchjb5zm"; protocol="application/pgp-signature"

--Sig_/ZNDR_qJYh3baf4EQchjb5zm
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Tom Ritter <tom@ritter.vg> wrote:

> I've put together a slide deck that aims to provide a 100-foot
> overview on little-t tor and Tor Browser. 100 foot, meaning I go into
> a lot of technical detail, but not 10 or 1 foot which means some
> things are definitely glossed over or handwaved a little. My
> consistency with the 'foot level' throughout the deck varies a bit,
> but I think it's decent.
>=20
> Before I post it on twitter or a blog, I wanted to sent it around
> semi-publicly to collect any feedback people think is useful. In
> particular:
[...]
> Slides are at: https://ritter.vg/p/tor-v1.2.pdf  Yes - it is long.

Great.

A couple of comments (about v1.3):

=46rom page 68:
| RELAY_EARLY - We don=E2=80=99t actually send EXTEND commands
| in a RELAY cell, we use RELAY_EARLY. If a node sees more
| than 8 RELAY_EARLY cells, it assumes you=E2=80=99re trying to make
| an infinite circuit and dies=20

This could be interpreted to mean that the node stops functioning
for the whole network (trivial DoS) while the source suggests that
it merely closes the circuit.

Page 73 could mention that the .exit notation is disabled by default.

Page 124:
| PubKey Authorization (Auth Type 2) - Functionally implemented at
| a different HS Address & one-password authorization per client

s/implemented at/implemented as/

Page 138 specifies bandwidth without unit of time.

Page 141 and 142 seem to suggest that parsing strings is more
likely to be vulnerable than parsing binary data. Is that intended?

Is the source of the PDF available under a free license?

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

Fabian

--Sig_/ZNDR_qJYh3baf4EQchjb5zm
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlVIvWIACgkQBYqIVf93VJ2YagCfZAYced6NRyfLAmfU7UqrYI3m
YRwAn0sq2lxYwm9gozK7GxkconatpPP+
=dYUe
-----END PGP SIGNATURE-----

--Sig_/ZNDR_qJYh3baf4EQchjb5zm--

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

--===============5085488352927022060==--

