Delivery-Date: Fri, 04 Mar 2016 19:10:16 -0500
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 7EBC71E08A4;
	Fri,  4 Mar 2016 19:10:14 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4412C3938B;
	Sat,  5 Mar 2016 00:10:08 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id BF61B39082
 for <tor-talk@lists.torproject.org>; Sat,  5 Mar 2016 00:10:04 +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 O5oaKna1Gbtu for <tor-talk@lists.torproject.org>;
 Sat,  5 Mar 2016 00:10:04 +0000 (UTC)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204])
 (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 98AEC3907B
 for <tor-talk@lists.torproject.org>; Sat,  5 Mar 2016 00:10:03 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org;
 s=mail2; 
 h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:To:From:Date;
 bh=dBeGZYqb1hUmv1yDFwqZYCLzZ7AN1iGKCssRxduC72o=; 
 b=U10r6FqO4GeovLbXilDonuAb1+D4qvwoumkg1MhFkOgVumBJqEHLwaru+577ngZJvQV99GWxSHAJPfJyKn4YNMukYit9HzjasbL5fE7ZBrBe89JncrQ2XRzULGK6Y3tfLXPHswEXnnQjhz/aRO47v2VRlmEb6oVVoRhL75Y9/d8=;
Received: ; Fri, 04 Mar 2016 16:10:01 -0800
Date: Fri, 4 Mar 2016 16:10:01 -0800
From: Seth David Schoen <schoen@eff.org>
To: tor-talk@lists.torproject.org
Message-ID: <20160305001001.GS7036@mail2.eff.org>
References: <1909EAF6-CFBA-41CA-BEA5-E63B98246594@riseup.net>
 <20160304200348.GA15259@inner.h.apk.li>
 <56D9EECF.4040605@riseup.net>
 <FE1CD58B-AB0B-402D-9DD9-45BDFFCC6C2B@riseup.net>
 <20160304205250.GQ7036@mail2.eff.org>
 <5E832B49-BE74-4E2D-9515-CBE6D0FF4A56@riseup.net>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <5E832B49-BE74-4E2D-9515-CBE6D0FF4A56@riseup.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [tor-talk] .onion name gen
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>

Scfith Rise up writes:

> I'm pretty sure that the onion address is generated directly from the private key, at least if you have every played around with scallion or eschalot. So what you just wrote doesn't apply in that way. But again, I could be wrong. 

Mirimir's reference at

https://trac.torproject.org/projects/tor/wiki/doc/HiddenServiceNames

shows that they are truncated SHA-1 hashes, 80 bits in length, of "the
DER-encoded ASN.1 public key" of "an RSA-1024 keypair".

So you have the space of public keys (indeed, it's considerably less than
1024 bits if you want to actually be able to use it as a keypair) and the
space of 80-bit truncated hashes, and the former is dramatically larger
than the latter.  So over the entire space of keys, collisions are not
just possible but are required and even extremely frequent.  On the other
hand, they're so difficult to find that nobody knows a single example!

-- 
Seth Schoen  <schoen@eff.org>
Senior Staff Technologist                       https://www.eff.org/
Electronic Frontier Foundation                  https://www.eff.org/join
815 Eddy Street, San Francisco, CA  94109       +1 415 436 9333 x107
-- 
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

