Delivery-Date: Wed, 24 Feb 2016 19:59:27 -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.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 D74661E050E;
	Wed, 24 Feb 2016 19:59:04 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4FF5239A28;
	Thu, 25 Feb 2016 00:58:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2AC7339A26
 for <tor-talk@lists.torproject.org>; Thu, 25 Feb 2016 00:58:53 +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 eqWMDsCDL0Ap for <tor-talk@lists.torproject.org>;
 Thu, 25 Feb 2016 00:58:53 +0000 (UTC)
Received: from ccs.nrl.navy.mil (mx0.ccs.nrl.navy.mil
 [IPv6:2001:480:20:118:118::211])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 0DA28399EC
 for <tor-talk@lists.torproject.org>; Thu, 25 Feb 2016 00:58:53 +0000 (UTC)
Received: from vpn212046.nrl.navy.mil (vpn212046.nrl.navy.mil [132.250.212.46])
 by ccs.nrl.navy.mil (8.14.4/8.14.4) with ESMTP id u1P0wmAY001123
 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT)
 for <tor-talk@lists.torproject.org>; Wed, 24 Feb 2016 19:58:49 -0500
Date: Wed, 24 Feb 2016 19:58:53 -0500
From: Paul Syverson <paul.syverson@nrl.navy.mil>
To: tor-talk@lists.torproject.org
Message-ID: <20160225005853.GP57127@vpn212046.nrl.navy.mil>
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>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <56CE3C0A.1060702@witmond.nl>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-CCS-MailScanner: No viruses found.
X-CCS-MailScanner-Info: See: http://www.nrl.navy.mil/ccs/support/email
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="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Thu, Feb 25, 2016 at 12:26:02AM +0100, Guido Witmond wrote:
> 
> I don't want *people* to exchange keys. I envision people to exchange
> names and let computers do the key lookup.
> 

The description below sounds a fair amount like Keybase (https://keybase.io)
Perhaps it would be helpful to contrast your goals with theirs?

aloha,
Paul

> For example, I get the id@site name from a nice lady I met at a bar.
> It's just like an email address but slightly different.
> 
> At home, I type in that address and my computer searches the validation
> service for the key. If all is well, there is *one* public key. That
> must be the key of the lady. If there is none, she may have given me a
> wrong address, or I may have made a typo. In these cases, it's like she
> gave a wrong telephone number.
> 
> If there is one public key, it must be hers as her computer checks for
> duplicates to protect her privacy. Or it's the name of some stranger,
> and after an embarrassing moment, I understand I can't reach her until
> we meet again in person.
> 
> If there are duplicates, she must find another site as it violated the
> protocol. She would do so as she won't get any responses from the people
> whom she gave her correct address. Those people would reject the
> duplicates and move on. (That's the protocol requirement.)
> 
> If she gave the correct id@site and there is only one public key, I can
> send her encrypted messages that only she can decrypt. Now we can talk
> in private. And when we use Tor, we hardly leave any meta data.
> 
> So the exchange of a human readable name - the id@site - implies that I
> can deduce the correct public key. The one-to-one relationship between
> names and keys makes it easy for humans to excahnge a name and for the
> computer to figure out the correct public key.
> 
> 
> So, to answer your question: people communicate id@site names, the
> computer verifies the uniqness properties to determine the corresponding
> public keys. The requirement to make the relation between names and
> public keys is key. Pun intended.
> 
> I hope this answers your question.
> 
> Regards, Guido Witmond.
> 



> -- 
> 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

