RE: Why are mail servers not also key servers?

Paul Wouters <paul@nohats.ca> Thu, 20 April 2017 23:41 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A592A128792 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 16:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kjGR8bmkrsNb for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 16:41:08 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6234C128DE5 for <ietf@ietf.org>; Thu, 20 Apr 2017 16:41:08 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3w8Fk8045cz3F8; Fri, 21 Apr 2017 01:41:04 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1492731664; bh=dKmdLFgjlaDlUuXazwtjd1LUeF8iSsx4lYI6FLqAXbI=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=aOFQJF11CTzYv1M6IB/MzRS123noLLZHBsFfuiD6ITl2Q6yKkQK1L0yhCVnCxlvdS pnEvFCv+RTEhli2PwA7FBWv7kRxtVy6IdXukYBhpxfyJ5pryek6EJASUDF5E6OvzdI EOY1+jsALW3zrBpk+sOYh3kLMEW3tKaVlpxDRtyI=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id Jy2GpNy1safK; Fri, 21 Apr 2017 01:41:00 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 21 Apr 2017 01:41:00 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 4D865418565; Thu, 20 Apr 2017 19:40:59 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 4D865418565
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 30A7F40D811F; Thu, 20 Apr 2017 19:40:59 -0400 (EDT)
Date: Thu, 20 Apr 2017 19:40:59 -0400
From: Paul Wouters <paul@nohats.ca>
To: Rui Costa <RCosta@alticelabs.com>
cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Why are mail servers not also key servers?
In-Reply-To: <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D3@PTPTVDEX02.PTPortugal.corpPT.com>
Message-ID: <alpine.LRH.2.20.999.1704201937001.18536@bofh.nohats.ca>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu> <B897A3A3-4A47-4C74-B79F-4F93C86A338C@gmail.com> <82ab9e4d-05ba-bc39-c7d1-bda6ee8d9be5@hawaii.edu> <20170420173551.GN25754@mournblade.imrryr.org> <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com> <063FA8A5-D94C-4537-8141-2A04374D4091@dukhovni.org> <09e03f86-69d4-27b8-4923-c68388cc426f@gmail.com> <20170420192604.GF2856@localhost> <alpine.LRH.2.20.999.1704201608320.13482@bofh.nohats.ca> <3BAB6CADBB6CA243A443E7C6674F2AB4082F04A1D3@PTPTVDEX02.PTPortugal.corpPT.com>
User-Agent: Alpine 2.20.999 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kn9Zv-6EByURXkaZ5wLc3c6m53s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 23:41:11 -0000

On Thu, 20 Apr 2017, Rui Costa wrote:

> So, can someone point me to some URL/documentation/https://mailarchive.ietf.org/arch/msg/ietf/xyz explaining the point on having keys/cryptography somewhere in between these 2 end points? (And thus i guess i'm saying i don't understand cryptography's point on scenarios other than what i think people have called on these threads "E2E".)

I want to send you an encrypted email. I need your key. I can send a
plaintext email asking you for the key. I have to hope that it really
reached you and that it is you who gave me the key and that the key
was not modified in transport.

versus:

You publish your key somewhere with a verifiable link of key to your
email address. Now your first contact with me will be encrypted and
secured.

People have different ideas of what minimums and maximums to use
for "verifiable link of key to email" (or even key to human)

Paul