Delivery-Date: Tue, 23 Feb 2016 14:32:53 -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 C7B211E06EF;
	Tue, 23 Feb 2016 14:32:51 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 16F893974F;
	Tue, 23 Feb 2016 19:32:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3CF7C3974F
 for <tor-talk@lists.torproject.org>; Tue, 23 Feb 2016 19:32:44 +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 lojoIaSLzgQS for <tor-talk@lists.torproject.org>;
 Tue, 23 Feb 2016 19:32:44 +0000 (UTC)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com
 [IPv6:2607:f8b0:4001:c06::231])
 (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 1C0E939738
 for <tor-talk@lists.torproject.org>; Tue, 23 Feb 2016 19:32:44 +0000 (UTC)
Received: by mail-io0-x231.google.com with SMTP id 9so226430611iom.1
 for <tor-talk@lists.torproject.org>; Tue, 23 Feb 2016 11:32:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=cyblings.on.ca; s=google;
 h=subject:to:references:from:message-id:date:user-agent:mime-version
 :in-reply-to:content-type;
 bh=yPU7dx76y3Ga/4xPr/D9ebumSYMZWoTc2XwZEDvsqNQ=;
 b=BFb6bekbhfBOlDRcNmf3CbGstVk6w8A9V7f136FYJQf0WnBx59CPoFdUiQqi7pRvv0
 86opaKsNUvoxrqpTZdpvxVCGIXI5sfh4vSJQYb/26DcQrCmyCxmunciA5pI41C1P1eNf
 kriWoZ+t1rEgZS0m48NhP/BuuUkW8hDEHhT90=
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-type;
 bh=yPU7dx76y3Ga/4xPr/D9ebumSYMZWoTc2XwZEDvsqNQ=;
 b=Uzoh7b2PciueyaDnzR6mnzfrMvo7rEqaud2CAfvfUjr3TEhriqVKYzxFCeYSeIzgGq
 pN9CXMj5zLCPxRLxULxml8i1xCZuqJe0ygWZiJt8rBsYxt2tDENmu4w8QSohKLZBde4/
 hYURCeO19DPEln/aFMpQKMQpx72qZe7nOQuTy0yZfGMmL7GLaW4E3LV8xX0rlVQ22C4p
 eg73DuOZZKtHvSQihdPMDO+ZKBcVucZIkJ0ixpW4TlmejGZU9fP0nBCErhJftQxryio/
 Jmf/kls9wsRRElea06ihyMFzzq+8pEGt+vtZOBmEmkMBPvkpSw4ernH4kWfHHr1PrXMu
 SpYw==
X-Gm-Message-State: AG10YOSncJFpiyLM7G6qvjazlGukJe/bWTfrKKg10EeF30icx/fiot6lsVdJhuWE9DkkpA==
X-Received: by 10.107.135.34 with SMTP id j34mr37222122iod.173.1456255961892; 
 Tue, 23 Feb 2016 11:32:41 -0800 (PST)
Received: from [192.168.1.2] (69-196-152-198.dsl.teksavvy.com.
 [69.196.152.198])
 by smtp.googlemail.com with ESMTPSA id f70sm14060886ioj.37.2016.02.23.11.32.40
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Tue, 23 Feb 2016 11:32:40 -0800 (PST)
To: tor-talk@lists.torproject.org
References: <56CB7795.7040501@witmond.nl>
From: krishna e bera <keb@cyblings.on.ca>
X-Enigmail-Draft-Status: N1110
Message-ID: <56CCB2F0.2060408@cyblings.on.ca>
Date: Tue, 23 Feb 2016 14:28:48 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56CB7795.7040501@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: multipart/mixed; boundary="===============8918999391955405989=="
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)
--===============8918999391955405989==
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="IkrjX486IVOo69eQJCKlUR8CCfltNaNED"

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

On 02/22/2016 04:03 PM, Guido Witmond wrote:

> If either the blogger or responder wishes to send a private message,
> they can use the others' persons public key after validating there is n=
o
> MitM. Message transport goes through the site. After a few round trips
> of messages, there is certainty there is no MitM.

The website http://eccentric-authentication.org/ says:
> With the use of DNSSEC and a validation service to check that each
> certificate is issued only once we can prevent Man-in-the-Middle
> attacks

Could you explain how you validate that there is no MitM, and why a few
round trips would make this certain?  Do we not have to trust the
validation service not to issue more than one certificate?  I.e., the
website or validation service can be the MitM.



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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEVAwUBVsyy9/p3cia4tegJAQIuVwf+JQ0/eMGHlpB22PMEBx8EMVPvwMyqRmG8
kU7OKWWZEngzsEc4nPvq3nsbAIQLaUCVYGZK30IlLHpdfuUGL+0icVspvd5eJi68
KRav9UsxHBKypoivNOZV+D+w3dq8cY6d9CtyWg8ElUVyHV+S2FeK2bqhUH+cwqW/
yC9eHF3sQxaAmFq/nywGoreFPUBcCtNFUTCWVlnmh+JGBwmKtZcu0U3Ts6obtoiY
D+nPaQCP0SEvvoptNOtF/MWEy27uixBJkJvCkZTlYCsMpXHhrmhpRAFx84WZykdW
Iov5BPB66/UgCySpEBHw4l6cPWMyD8mKjp+SD1T2BE1nITyhm0HBug==
=otY5
-----END PGP SIGNATURE-----

--IkrjX486IVOo69eQJCKlUR8CCfltNaNED--

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

--===============8918999391955405989==--

