Delivery-Date: Tue, 05 May 2015 10:15:22 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,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 0AA2C1E041D
	for <archiver@seul.org>; Tue,  5 May 2015 10:15:20 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7F33934D44;
	Tue,  5 May 2015 14:15:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 6ABF934C29
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 14:15:13 +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 ct8KaKym7FMD for <tor-talk@lists.torproject.org>;
 Tue,  5 May 2015 14:15:13 +0000 (UTC)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com
 [IPv6:2a00:1450:4010:c04::232])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id E138C3478D
 for <tor-talk@lists.torproject.org>; Tue,  5 May 2015 14:15:12 +0000 (UTC)
Received: by lbbqq2 with SMTP id qq2so129436771lbb.3
 for <tor-talk@lists.torproject.org>; Tue, 05 May 2015 07:15:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:content-type;
 bh=ZZ5incdFruBClc1+GIOYV4zIxaC3whJ7+CIOCe+SjaQ=;
 b=qqWPugT1DyspKNAokTnW8e6VN4rRp5vIDqS+RCEXfmZlQq+6N9vQwlmlYeZAzfaSWE
 GK37EXeWvuBmztpOR+o2EKGqwHMRcYxnJM/rmF7hzjm2pf13BB0AXTyrw4cvhi3NXtV5
 iI2tPkNC4L7TdJcqBiBL+BPgDpaJydA5BDlZRWpIniiqQU+SU1LUiKNrfqgKOJCuGv+d
 45EhPxoedjQNwKQacQJ9THwGo59khFC9wj8sQ1+m2XwfiguZ39izctweAMTJ9qdrvEWN
 Y6k6NXW6tWaFmSwjujB7D1jbCBxp+47X2p2hpulfD/aYDflQbMmOe4JhF2amK8OuErnF
 rtlg==
MIME-Version: 1.0
X-Received: by 10.112.12.68 with SMTP id w4mr23820366lbb.87.1430835309743;
 Tue, 05 May 2015 07:15:09 -0700 (PDT)
Received: by 10.114.27.6 with HTTP; Tue, 5 May 2015 07:15:09 -0700 (PDT)
In-Reply-To: <20150505114925.3682DAE418@smtp.postman.i2p>
References: <camtdts-_bhhxb76-_us8gx6ydh2dppmh4-d6utibqghjaulrna@mail.gmail.com>
 <cajvra1s3ttx=hmdmrefvawot1bi18zh_ztbgh8g+s_7hwoddew@mail.gmail.com>
 <3d3832de66f.000004abbeatthebastards@inbox.com>
 <cajvra1ssz4rmw=s8yqyhkuakvyzbzaxlqfj_fawg3xuccsm90w@mail.gmail.com>
 <5545929b.10805@riseup.net>
 <camtdts9j65qtapqtk+tazq4o=spf9jxsrbhgz6xx8svjc6_ahq@mail.gmail.com>
 <camtdts9jo4rypqx+esro4pho2zag6gytjwdsxslenaq6a+026w@mail.gmail.com>
 <camtdts9mqhmkq+fqn7-gkmugnr3nhf_2a-fqunr_h0txa4pa7g@mail.gmail.com>
 <cajvra1s2um0d=om3bmf0ronowrdi41fvac=jprwuq9z+cb8vwa@mail.gmail.com>
 <CAMTdTS86dvRjiAOCJEeqSo-fX77XDZvKNWxTPOVsy+OFRR3pOg@mail.gmail.com>
 <3EBC4A37DD1.000005A8beatthebastards@inbox.com>
 <CAMTdTS8=A+j0wzpHn08gmYjoJMKtgH_K7b=_9nAdadGirXO1Cw@mail.gmail.com>
 <874mnsbkqc.fsf@example.com> <87zj5ka5u3.fsf@example.com>
 <CAMTdTS_rBxgKx=8=GDezvFCAR6gdasTo6cHkFPca8+-u15rZPw@mail.gmail.com>
 <20150505072215.C45DEAE41B@smtp.postman.i2p>
 <20150505114925.3682DAE418@smtp.postman.i2p>
Date: Tue, 5 May 2015 07:15:09 -0700
X-Google-Sender-Auth: AckbzmyIhDaRq3AHXvPozX1Kebc
Message-ID: <CAMTdTS8g4JFUpczzp9dga_6WibNw1GZ3pg0AxcCVCd4wbJK8dA@mail.gmail.com>
From: benjamin barber <barberb@barberb.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Meeting Snowden in Princeton
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>

I dislike the notion of the central directory auth, while not a SINGLE
point of failure, relying on someone else to know who to trust, is great
until you discover that the trust was underserved.

Operational security also seems to be glossed over to laypersons, which is
why I use to a solar powered computers running tor, that I network with a
private VPN server that I have running in germany.



On Tue, May 5, 2015 at 4:49 AM, str4d <str4d@i2pmail.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> W. Greenhouse wrote:
> > Some degree of centralization of the directory is, for now, the
> > only way to prevent an attacker from owning everything simply by
> > dumping a lot of bandwidth onto the network (what Lizard Squad
> > attempted to do). Networks like i2p and bitcoin are to a greater
> > extent vulnerable to that than Tor is,
>
> As with everything, it's a question of balance. Tor errs on the side
> of centralization, which enables it to easily detect bandwidth dumping
> and block arbitrary routers with quick turnaround, but that is a lot
> of power in the hands of a (trusted) few. It also does nothing against
> e.g. carefully-planned slow Sybil attacks.
>
> > because i2p and bitcoin didn't even consider resistance to network
> > sibyls as part of their design.
> >
>
> The original I2P devs *did* consider Sybil resistance while designing
> the network, and did include scope in the network architecture for
> e.g. HashCash-like mechanisms, but ultimately decided to take the
> decentralized route, and designed the network on the assumption that
> no router is trusted. As for detecting and inhibiting Sybil attacks:
> it is still possible to detect bandwidth dumping (one example I recall
> was a research group starting up a bunch of routers), and we do have
> the ability to block routers, but only via router upgrades. So yes, it
> is certainly more difficult right now to impede Sybils on I2P. But
> there is more focus on making the attacks that Sybil enables harder to
> carry out (because a Sybil on its own is not an attack), as well as
> general network growth to make obtaining a large enough network
> fraction more difficult (we estimate there are currently around 25,000
> I2P routers).
>
> str4d
> -----BEGIN PGP SIGNATURE-----
>
> iQIcBAEBCgAGBQJVSK4iAAoJEBO17ljAn7Pgz1AP/1FkitJsLNDZzB3q8+xNRb2Q
> qS669IdXkin1oFPr/LeZ6zlic2N7cqgVtYhTkVKaq03w9f4P52EqCgN7ZzNUCShK
> xvx2bM/EN/fhNm1xHdTLMQRXvD2X3cpHPoc7MVPyl8fhUNe09Xivdm2NwusMso7y
> LQmkAJXoBf6uHVVyCZDvLYXuMBiXpSMlpbFWqOJJEyTDbbC1Wo6JScxFShJ0Dd3S
> Htz01LjdMLy9TcDhsiy4kZrRev+It2sARe6cUyEHYhJRt1elraVveW4VhdthlAS2
> VK78XWvlMKRZDEuRVK7Gm0chkLK4gtDgEXnsEwr7EAwXkyb2VBHuyMVo7ISpH7sT
> 2eRTMmlBINXqV8I5AeIRXc3SPQRg7gqmx7vyw+khAnjgtjWWuEKWiBHrxZ/jLDVR
> rcr06+CXLuYthae038QL6qUHCP5LUu6uXGXxBeAJ4Fr/Ig8+SiMda+Ctv2a/hBmd
> kSklCnpeh4/gFo8VUZlyMLF+PEK8d5EtEDBHLIGITQAqQSZb03xpv7KIDeJ4D/uc
> vIP5f25dCguaMxzNO0gpk3ikeZDo2zkt/PRd6VUh2cYUU1K4SL0jYpDBajX3/OKG
> b2/CoOz+pSDVgvYDjupyQ0vFDgtvUckOPfxR48v+bhcH5v9HFUo4iezSX5zNZhd0
> eItO8jzcv887nVAAGcAG
> =E7Pe
> -----END PGP SIGNATURE-----
> --
> 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
>
-- 
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

