Delivery-Date: Wed, 17 Sep 2014 18:08:52 -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.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
	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 8E5C81E0B2A;
	Wed, 17 Sep 2014 18:08:51 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7521C2D6F2;
	Wed, 17 Sep 2014 22:08:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 1A5D62D2D3
 for <tor-talk@lists.torproject.org>; Wed, 17 Sep 2014 22:08:46 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 htN2Oq_fM-AV for <tor-talk@lists.torproject.org>;
 Wed, 17 Sep 2014 22:08:46 +0000 (UTC)
Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com
 [IPv6:2607:f8b0:400c:c03::234])
 (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 EAD5C2D0A7
 for <tor-talk@lists.torproject.org>; Wed, 17 Sep 2014 22:08:45 +0000 (UTC)
Received: by mail-vc0-f180.google.com with SMTP id hq11so1821vcb.11
 for <tor-talk@lists.torproject.org>; Wed, 17 Sep 2014 15:08:43 -0700 (PDT)
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
 :cc:content-type;
 bh=ig9yMy64oJr5Z0ljyvJNGtqqFwmEKYnD7ouiUYGXYlI=;
 b=eLDgcgZ/J+ezk6wdzPK/ci4xAdN1cmH92Mm/McShgslvWZmC0BzN7djhiC793wtBxH
 Luaus6wUtEHExWd0disIjXrr5IqaxlAOV12CL0o4hl2vHA7Ti5RUW3UhyxIivL1Rm7a+
 SoF8oCwM4K9ZvvgZWhnPS1PedLgq3lfiU/5R8YwQppJIuURnlhXtIElUU+Xx54yvxJxf
 WQeQBce28aVlKRGxXAqC9gF/WrMW/iET153QIkX3eMA1AGxyNe3TPQFWsOoAHaeRRq4A
 l5mZr4fyFdDKcFb0yuADcRq47UhAdXFmwMqNnzLvOZ9aqSkreud12DxdHb8S7waokku0
 nPvg==
MIME-Version: 1.0
X-Received: by 10.220.68.208 with SMTP id w16mr49919vci.79.1410991723189; Wed,
 17 Sep 2014 15:08:43 -0700 (PDT)
Received: by 10.221.64.74 with HTTP; Wed, 17 Sep 2014 15:08:43 -0700 (PDT)
In-Reply-To: <156b8eed2e9dc784c15c238afc028330.squirrel@bitmailendavkbec.onion>
References: <156b8eed2e9dc784c15c238afc028330.squirrel@bitmailendavkbec.onion>
Date: Wed, 17 Sep 2014 18:08:43 -0400
Message-ID: <CAD2Ti29evbkQ5vRJxkEbx=L+hKypUsVdZY7aFuCkktXU=xMpsA@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Cc: cypherpunks@cpunks.org
Subject: Re: [tor-talk] wake up tor devs
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, Sep 17, 2014 at 5:04 PM,
<BM-2cUqBqHFVDHuY34ZcpL3PNgkpLUEEer8ev@bitmessage.ch> wrote:
> Why is Tor wasting time in implementing secure hidden services? Why not
> copy from here if they are doing it right:
>
> Tor     I2P
> Cell    Message
> Circuit Tunnel
> ...
>
> Why not distributed directory authorities and hardcoded?
> Why not secure tunnels independent of guards?
> Or does Tor want to remain less secure?

Yes, there should be more comparative analysis
of approaches amongst all the current networks. Create
a dedicated group that publishes such things on a darknet wiki.
Hold not just project specific meetups as is done today, but
genuine summits amongst all such projects that puts
their specific projects aside and determines what models
might best suit the next 10-20 years. Determine whether the
community is too chained by legacy project/product entrenchment
to adopt new better approaches that have come up in research
since they themselves started their own projects. Find
any worthy new techniques and peel off interested developers
into new projects. Try to ensure that big well known
projects aren't soaking up all the fanfare/funds when
equally valid small projects, or new projects would benefit
the world the same or more than the gorilla in the room.

For example, there seems some merit in filling your
internode links with chaff padding up to the bandwidth
limit you configure in order to mask both when and
how much you are communicating.
But it does not seem any project is doing that?
Perhaps because chaff transmission/management/security
models are not well developed. Or just the 'woah, bandwidth'
reaction, which in reality of the simplest design only
affects you and what bw you were willing to purchase
or experience anyway (as when operating under a
non-chaff network with a given/high utilisation condition).

Another example... there was, or is, at least one group
accepting funds and then running some of the various
overlays equally at once... tor, i2p, freenet, cjdns, mailmix.

Take some time to step back and see what together you
can do with the big picture in all areas... research, development,
operations, marketing.
-- 
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

