Delivery-Date: Sat, 30 May 2015 02:40:37 -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 A7BC91E143B;
	Sat, 30 May 2015 02:40:35 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 78AD934D40;
	Sat, 30 May 2015 06:40:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9BE0A3496A
 for <tor-talk@lists.torproject.org>; Sat, 30 May 2015 06:40:25 +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 oFhz8x-ZTVdT for <tor-talk@lists.torproject.org>;
 Sat, 30 May 2015 06:40:25 +0000 (UTC)
Received: from lo.psyced.org (lost.in.psyced.org [188.40.42.221])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "lo.tobij.de", Issuer "lo.tobij.de" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 3FD8F33056
 for <tor-talk@lists.torproject.org>; Sat, 30 May 2015 06:40:24 +0000 (UTC)
Received: from lo.psyced.org (localhost [127.0.0.1])
 by lo.psyced.org (8.14.3/8.14.3/Debian-9.4) with ESMTP id t4U6eL9Z003150
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
 for <tor-talk@lists.torproject.org>; Sat, 30 May 2015 08:40:22 +0200
Received: (from lynx@localhost)
 by lo.psyced.org (8.14.3/8.14.3/Submit) id t4U6eKCs003148
 for tor-talk@lists.torproject.org; Sat, 30 May 2015 08:40:20 +0200
Date: Sat, 30 May 2015 08:40:19 +0200
From: carlo von lynX <lynX@time.to.get.psyced.org>
To: tor-talk@lists.torproject.org
Message-ID: <20150530064018.GA2622@lo.psyced.org>
References: <CAD2Ti29GdabbDUMK9fXBR00RJ4Fbg-VHNN9eFwOOUDgecGBeHQ@mail.gmail.com>
 <3997552.s7nlVdOtgF@kerdohl>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <3997552.s7nlVdOtgF@kerdohl>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [tor-talk] [onioncat] Paper for OnionCat and Tor New Crypto
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 Mon, Feb 16, 2015 at 09:19:51AM +0100, Bernhard R. Fischer wrote:
> On Sunday 15 February 2015 12:59:08 grarpamp wrote:
> > Hello.
> > Is there an English version of a paper (or presentation) for this?
> > 
> > Bernhard Fischer - OnionCat und Tors neues Kryptosystem
> > https://www.youtube.com/watch?v=Zj4hSx6cW80
> 
> Unfortunately not yet.
> I'll write a proposal in English on my blog.

Sorry, I only watched this presentation now.. months later.

It didn't click with me why you would do such a hack to
allocate a "next" onion if all you need is a way to upgrade
an 80 bit hash to a full public key. Well, I presume Tor
will maintain backwards compatibility with 80bit onions
anyway, so you can always just look up the 80 bit hash and
find out which key owns it. Should Tor one day indeed upgrade
its crypto it could generate 301 redirect messages from the
old .onion names to whatever comes next. Or it could pin them
in the router. I don't see the need for the procedure that
you proposed.

Also, providing a global cryptographic IPv6 address scheme
in the spirit of cjdns looks like a false problem to me.
Cryptographically authenticated IP numbers do not solve the
problem that DNS can be spoofed to return the wrong address.

Therefore if people want an address they can refer to and that
will always be valid, they can use a simulated TLD which uses
the entire public key, much like the .zkey proposal. There is
no advantage in mapping it into the IPv6 address space, losing
bits in the process.

If instead people want an address they can memorize, then they
need a new naming system that doesn't mess up security and/or
look-up privacy. What about GNS for that.

I think the cjdns/onioncat style is the wrong approach, even
if it gives everybody an excuse to check if thep rograms 
are indeed IPv6 compatible, and kind of has an air of a neat hack.


-- 
  E-mail is public! Talk to me in private using Tor.
  torify telnet loupsycedyglgamf.onion		DON'T SEND ME
          irc://loupsycedyglgamf.onion:67/lynX  PRIVATE EMAIL
         http://loupsycedyglgamf.onion/LynX/    OR FACEBOOGLE
-- 
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

