Delivery-Date: Thu, 25 Feb 2016 17:55:19 -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 03A621E0A69;
	Thu, 25 Feb 2016 17:55:17 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id CD8CD39AE8;
	Thu, 25 Feb 2016 22:55:12 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5656739AF8
 for <tor-talk@lists.torproject.org>; Thu, 25 Feb 2016 22:55:08 +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 SIOyU7L6ulwm for <tor-talk@lists.torproject.org>;
 Thu, 25 Feb 2016 22:55: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 DC7A239AAC
 for <tor-talk@lists.torproject.org>; Thu, 25 Feb 2016 22:55:07 +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 1C9AFC0684
 for <tor-talk@lists.torproject.org>; Thu, 25 Feb 2016 22:46:49 +0000 (UTC)
Message-ID: <56CF8455.90204@witmond.nl>
Date: Thu, 25 Feb 2016 23:46:45 +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>
 <56CE3C0A.1060702@witmond.nl> <56CEDE2F.20407@beroal.in.ua>
In-Reply-To: <56CEDE2F.20407@beroal.in.ua>
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="===============3899281470422680431=="
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)
--===============3899281470422680431==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="ECVSNJIsApwEdPi6tSP8DqMlNU4V9AxPr"

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

On 02/25/16 11:57, me@beroal.in.ua wrote:
> A magic wand is a solution. :-)

Luckily, any sufficiently advanced technology is indistinguishable from
magic, so to my audience - the normal user - it looks like that :-)

> Though I don't understand your protocol, I don't like id@site names.
> That site belongs to a corporation, so I depend on a corporation which =
I
> can't control.=20

There is good news, anyone can run this protocol on any domain. It's not
limited to companies. In fact, running it on your own domain gives you
the security that no one can be messing with it.

> There is a more fundamental problem with human readable
> names. There is competition for nice names like "sex" or "casino", for
> example, in the domain of domain names. This competition is resolved
> with auctions. So a human readable name is paid, and its owner depends
> on the registrar.

Everything has a price. Only sunlight is free, after paying the
rent/hotel/wood for the fire under the bridge to survive the night. :-)

Seriously, the requirement is that each sitename is unique and can't be
abused by others than the owner. That way, each user@sitename is unique.
And that's to make the one-to-one relationship between names and keys.

There might be stronger systems than the current DNS registrars. A
sitename in a Namecoin system springs to mind. The issue is that it's
used by a very small group.

But take it from me, I'm in favour of stronger naming systems than DNS.
It's quite brittle in respect to coercion.

Public key fingerprints are a solution to both problems.

Except that people won't check these things. You do, but I want a system
that works for people who don't/can't verify those.

Cheers, Guido.


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

iQIcBAEBAgAGBQJWz4RVAAoJEHPd8GglaNRmbz0P/0c2oho60wmvPlPhyQce704l
pF9lJyq4r42accBs2h1zCki45LfurBHZ3skBL/6QMf1bp/SowGbfpsGsUr3FnqAO
KOIq6W0AfMm7PtBHqX9L7b6JB98CY4+IdExlmDWiT/+8WWtrkxs0H32kzVKKTnOu
kLbMwN7uBq2AOkEGfU7OMruWkwLreD4uDz0OOWuNfTg4XgrxSUECjzBBHDvaQvg1
KEWqmZSEZ6Wbuyb1hMpyXtSL+nwfsGI2AbHeJTqf0Tc7YSo+EPTJ/H0r6Z2ZVNbz
dfOyGYCZrF7LAofkUEQj52Bju+Q7+bxkJ0LtFewEreTYiZsc/RSmaSvNszdpd6xI
3q3bbFMMy/WeHMDAsr3bXm9SzDfzNmq8RPd2lneecFeJu/EaDvRxt2VJJC1D5PHc
btvach0fZdkY0Psd+KMJO/VKfrOIff4YxT27YfCGBILNEy0Wr5vQJSuWerCDNtHk
tbb6dmmtp0gF96G4cNwQG90tWCs/2eSh7GH3hiI54uSwvepRWpvjrbfMuDoohg4I
d7Ngzx9jYJVbtUyoGuSBlYZXdoQjUb6sex1Zy9zd1AnCyQxM9huMd1KkeuO1gZxY
ZzzGFZFZxuRb+X2YF4EaXRTLQtiN3wcqW7SWTnEXrR4EHIOdmrTJjTX7pabp0IxK
cWT5koDBT3iUgq5K8gs5
=kPRj
-----END PGP SIGNATURE-----

--ECVSNJIsApwEdPi6tSP8DqMlNU4V9AxPr--

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

--===============3899281470422680431==--

