Delivery-Date: Sat, 27 Feb 2016 13:43:22 -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_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,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 88D1E1E01FC;
	Sat, 27 Feb 2016 13:43:20 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7C72F39DEB;
	Sat, 27 Feb 2016 18:43:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5345D39DBB
 for <tor-talk@lists.torproject.org>; Sat, 27 Feb 2016 18:43:09 +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 7edpbzoXPh6I for <tor-talk@lists.torproject.org>;
 Sat, 27 Feb 2016 18:43:09 +0000 (UTC)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com
 [IPv6:2a00:1450:400c:c09::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 0773239DB3
 for <tor-talk@lists.torproject.org>; Sat, 27 Feb 2016 18:43:09 +0000 (UTC)
Received: by mail-wm0-x232.google.com with SMTP id l68so11987446wml.0
 for <tor-talk@lists.torproject.org>; Sat, 27 Feb 2016 10:43:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=subject:to:references:from:message-id:date:user-agent:mime-version
 :in-reply-to:content-transfer-encoding;
 bh=8wDZWH5v7sZA84fkM3YX8osggqBWofyecJiNEKioFtM=;
 b=tvEeGhj92FG4T2zbwn9moCVeN1S2y64TSUZcgmLsehT2seqt3a++hbFD0C3+tIUpGq
 aqLDJ20QLCuogtsAzi2XwMQZTSrFUWrdcsixNrC3cMs7sy8jr8YczwofpcoMYNdUzVXu
 P1tkd/M2SMXQm8gA349tBqR+VLmiCTPzrn5Taed/gAOmtq0d6tarehtReRSTroZ1PQUI
 boZjqENOAEuD8X5XT707UJwOaLz8AR+1Ybcnt+OLxhmyVqK/HgdiyuSLeaOKROpl/Ouw
 MfJV160BMB6xITv3cR/KXcZQAHJvh4z8LHxJdjJw7hsJZn19PhO2sLC38fe6x+B32BdF
 f/3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:subject:to:references:from:message-id:date
 :user-agent:mime-version:in-reply-to:content-transfer-encoding;
 bh=8wDZWH5v7sZA84fkM3YX8osggqBWofyecJiNEKioFtM=;
 b=S/UF998YskpoJOs6aOqKUY6bcsOBdRN539AIGGG9spzQkEDuERm2NsDJM6VZKNL0Hk
 3yRqFCfXgj8Dv7a4jzeWIxpVOZrqkUfzh7dWGoEYMqSvPVR5li5pW/ick4eyz+CWiW2A
 /VLNxpuJDyu6s6H7eV2aux5NbpE3CsjLclSDG7gkzj/DKA3mDiP0mlEu+0K2mIn8DuEn
 JfGrvIVZ4Er9oBkMOqeYMp2IsgH+kg1KaSsOvAC9+yZ3zgxZIDejeC6866lzjOiGIDPZ
 sEzClRV1zF3zolq9qdYcSZBbMDe7kNFnzazUIogq7PCenh0muy4Dy4rb3VhWuKbnIdlu
 50QQ==
X-Gm-Message-State: AD7BkJIbqplEUjxkY+wmzV5zQYmT1BtYbPICq70slGf0BQcCTiWSZmm5UppenjvOPqFiFw==
X-Received: by 10.28.128.138 with SMTP id b132mr4043707wmd.26.1456598586149;
 Sat, 27 Feb 2016 10:43:06 -0800 (PST)
Received: from [192.168.1.10] (ANice-654-1-176-246.w83-197.abo.wanadoo.fr.
 [83.197.153.246])
 by smtp.googlemail.com with ESMTPSA id c136sm8228532wmd.3.2016.02.27.10.43.04
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Sat, 27 Feb 2016 10:43:05 -0800 (PST)
To: tor-talk@lists.torproject.org
References: <56CC3191.1000402@beroal.in.ua> <56CCA590.5020506@witmond.nl>
 <56CCAA26.8070609@beroal.in.ua> <56CCC954.6080102@witmond.nl>
 <CAB7TAMmRBgO2FPvV8rpW7ZaWZ14hbvQ_3NZyhENi4bN1aKDBuw@mail.gmail.com>
 <56CCE201.7070706@witmond.nl>
 <CAB7TAM=kJZG=8eEka2sNBjyh-T7omJ7B1oBga--eDej6F_1-=A@mail.gmail.com>
 <56CE28F7.4040800@witmond.nl>
 <56ce2e4d.8518370a.50ae9.ffffb299@mx.google.com>
 <56CE3C0A.1060702@witmond.nl> <20160225005853.GP57127@vpn212046.nrl.navy.mil>
 <56D0B632.40305@witmond.nl>
 <CAOsGNSSATd0AOwfVEV+Ejp32+7BE7SfvTXnVi1M2DPTVLVBGqQ@mail.gmail.com>
 <56D19400.8050405@witmond.nl>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Message-ID: <56D1EE3F.90708@gmail.com>
Date: Sat, 27 Feb 2016 19:43:11 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56D19400.8050405@witmond.nl>
Subject: Re: [tor-talk] Tor for everyone;
	introducing Eccentric Authentication
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="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>



Le 27/02/2016 13:18, Guido Witmond a =E9crit :
> A hash table does a lookup from HASH(data) -> data.

No, a DHT stores some data about something referenced by something
looking like a hash

> =

> When I retrieve the data, I can calculate the hash and determine if I
> got the correct data.

When you retrieve the data you can do whatever you like, of course it's
better to implement the required mechanisms to prevent others from
spoofing data.

> =

> What I want is a lookup of name -> public key.
> =

> I could set up a DHT that does HASH(name) -> public key but there in no
> user name in the public key, so there is no way to calculate that I got
> the correct data.
> =

> Would I create a DHT based on HASH(name) -> certificate, where
> certificate is {name, public key, CA-signature}, I still have to
> validate if I got a result from the correct CA. The question that
> remains: who is the CA chosen by <name>.

I am not sure to fully understand your CA signature model, why can't you
store [name,public key,CA-signature,CA-key,CA-name]?

In my previous answer the P2P system on top of the peer/entityID system
would implement peer discovery based on a DHT but not only, peers can
discover each others based on information they get from other peers they
are connected to.

Back to the DHT they could register [peerID, public key, how to reach
peerID] or to match your case [peerID, public key,
entityID,entityID-signature, entityID-key], where peerID is the
fingerprint of the public key, on the closest nodes from peerID, where
the nodeIDs (closest nodes where is stored the data) can be the
fingerprint of temporary keys (like onion keys), so people can't chose
their nodeID and fake the DHT.

The peerID info would come from matching a name in something like a
blockchain (where entityID are referenced too), where you can store as
many IDs as you like (and in your case if I understand correctly map
peerIDs with entityIDs).

So what's the benefit of a CA model here?

-- =

Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
-- =

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

