Delivery-Date: Wed, 24 Feb 2016 18:35:30 -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 EFEDD1E0068;
	Wed, 24 Feb 2016 18:35:28 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A138639990;
	Wed, 24 Feb 2016 23:35:23 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D1521399C3
 for <tor-talk@lists.torproject.org>; Wed, 24 Feb 2016 23:35:19 +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 uAoBeAhmt129 for <tor-talk@lists.torproject.org>;
 Wed, 24 Feb 2016 23:35:08 +0000 (UTC)
Received: from mail.witmond.nl (unknown
 [IPv6:2001:980:71b2:1:6887:4dff:feed:7c36])
 by eugeni.torproject.org (Postfix) with ESMTP id 385EA39974
 for <tor-talk@lists.torproject.org>; Wed, 24 Feb 2016 23:35:08 +0000 (UTC)
Received: from [IPv6:2001:980:71b2:1::6] (unknown [IPv6:2001:980:71b2:1::6])
 by mail.witmond.nl (Postfix) with ESMTPSA id 1D202C0C60
 for <tor-talk@lists.torproject.org>; Wed, 24 Feb 2016 23:26:07 +0000 (UTC)
Message-ID: <56CE3C0A.1060702@witmond.nl>
Date: Thu, 25 Feb 2016 00:26:02 +0100
From: Guido Witmond <guido@witmond.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Icedove/31.8.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <56CB7795.7040501@witmond.nl> <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>
In-Reply-To: <56ce2e4d.8518370a.50ae9.ffffb299@mx.google.com>
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: multipart/mixed; boundary="===============2155389408349797129=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============2155389408349797129==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="4JF20jpgEipiA99LGWiKjJoMI0pN5OgWN"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--4JF20jpgEipiA99LGWiKjJoMI0pN5OgWN
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 02/24/16 23:26, juan wrote:
> On Wed, 24 Feb 2016 23:04:39 +0100
> Guido Witmond <guido@witmond.nl> wrote:
>=20
>> My drive is to make key exchange happen as a natural part of normal
>> interactions between people.=20
>=20
> 	So teach people how to exchange keys.

Teaching is not a solution. See Peter Gutmann's book Security
Engineering. 800+ Pages of disasters with security. Depressing and
enlightening ;-)


>> Not as a separate step that could be
>> neglected, forgotten or done wrong.
>=20
> 	Ah you want key exchange without key exchange? That is, of
> 	course, absurd.

I don't want *people* to exchange keys. I envision people to exchange
names and let computers do the key lookup.

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.


--4JF20jpgEipiA99LGWiKjJoMI0pN5OgWN
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJWzjwKAAoJEHPd8GglaNRmpRkP/A1hd+lPTXzkzCB4Y96Fktlg
7jpCkP8MY8DEtcYOUhory2CnYrfwE2SPHc1VIW3x1uy6joxMemS2NWN5Pd0JqG1F
pBfpT+UCIZae6wav9ZusCz9QT3epwk3cidzK81DhgNV8bQRWXjFSOqKjesF/Tnfd
nkkB56OVijmTJeYz3H3GhTlK/BXPz/3esbzpqAbFX5L7A1p7eyh/CfWCkQniqFku
1PMb+aSKCeNQbHmhh5o4dg82kqLbcZyzK/A79s7sEoawNf1yXHnUOXnS2ubvBjFq
+HTm9B3DozgaLVHxdqz51ZddT/RoMbYVZeN3gv12u6jkpH3UHEjFdfKZo5wTsCRB
VgbQeozQk7+BmLSLhMo2OMp2OoGtY6XmISCBI5YhsqMM+EIncXYCenNpe5v33apH
T7wNOE0NdJaJ/l5iTrfX6KLo0Xr5b/qiwjWacJIWZWH4nV0hmAAKOGKTJ019zwQa
/t5ojOa3YUcEkMoLb41nSL26bm6dMxc7sXm2Ywt1jyXYnPld6zKD4wIUf04yw+TK
vM62zEjsh7A7pSyrwSvkPnq3h18noOPzU8uBHE7+69w4TAWddOq7YJWY6nn1jCSb
8YAAw0lsh8+W2sLGfKEEfw7ozeP3c+e4q7qgIKkIY3tqMrMbCYqedwW9HPdoOku0
VDSAX2+bQXbrjGl/piXp
=/0q+
-----END PGP SIGNATURE-----

--4JF20jpgEipiA99LGWiKjJoMI0pN5OgWN--

--===============2155389408349797129==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2155389408349797129==--

