Re: Why are mail servers not also key servers?

Doug Royer <douglasroyer@gmail.com> Fri, 21 April 2017 03:35 UTC

Return-Path: <douglasroyer@gmail.com>
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 2A0FC129533 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 20:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 nqDhqayLISmV for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 20:35:39 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA87012EAA5 for <ietf@ietf.org>; Thu, 20 Apr 2017 20:35:37 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id j201so76932312oih.2 for <ietf@ietf.org>; Thu, 20 Apr 2017 20:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to; bh=wuzTclmvFyP+0VRPCv6hGo/RBwTPclCi47QVXQ3uzM4=; b=fCPUhcSJfbjEQcnZXH6e/fDrryU+5VTwZnjE2WwOUn4gX2dcTFOvKEsyjrRYNx9l8q RZxqtCvZ895OA+AajkBNFDwzYPD1NdBTlNAq0kUUM7vjS9tTockB3ZzbNabRh6V0NMh4 3Q8vykLTX0pw4GhiSG9fWarUoKMt4BrOU5pO6FXSz4i9YGm2wPODJfoE0qT5SMXCmzVb KA3lQfWv1GhJGyAnqaSg6prn96oS7fAS1GCbdVjkqunJRk8KKpvDpkzBbmNcco9inkAJ ggB5EQwrt/F9oXB+4dl7ZQsvH6FAIECVcDbe80olHXSSWKE9viYKkDjXWhCwNZCBgaGc R5CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to; bh=wuzTclmvFyP+0VRPCv6hGo/RBwTPclCi47QVXQ3uzM4=; b=FbdxZxVAMz32wTpcysIJv684FwQtWvn2P4APrxdcZOUh0ypRkStsRTSSbH2bBPkmqm wQv5vsBRQgdiqeXzgDCHHn/7OoHpsPvQ1jPdf7I7iR55Kk85K6XQXKp4BMYIpXvnouDO z+UU1CLNYrBucsT0FepC9nFKxOydbRrPosqybvgy2qyROlB7B6dIvvKh+f21642tT3px FCL+507AczCwbHm4XlUo7EHDTsebNnB6IX/m21HqxSNXN5o0gJp/xiBlyHUN4z1FJlN7 Sz3AcAMVbP6+yi3kU/sZ3N+It5ofM8p4PlugOFHCuhleI26uitFIdhuTBezCKJDR8uqL wjYQ==
X-Gm-Message-State: AN3rC/6wNBZikhSC0r7bfEd1Q6nPNxQqOfXCMS/Ei2Q8FBMsDT2LT8+Z rG28Lb59ptJ1kARj/iw=
X-Received: by 10.157.22.161 with SMTP id c30mr6233516ote.247.1492745736686; Thu, 20 Apr 2017 20:35:36 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id n64sm3540561oif.22.2017.04.20.20.35.34 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 20:35:35 -0700 (PDT)
Subject: Re: Why are mail servers not also key servers?
To: ietf@ietf.org
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> <alpine.LRH.2.20.999.1704201937001.18536@bofh.nohats.ca>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <c4b3cfbe-9420-e171-8d0f-18d21b6e451d@gmail.com>
Date: Thu, 20 Apr 2017 21:35:33 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <alpine.LRH.2.20.999.1704201937001.18536@bofh.nohats.ca>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms070000080306040105040208"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7JlZQ79KAfRmyj9RcOUE4ADd9Mg>
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: Fri, 21 Apr 2017 03:35:42 -0000

On 04/20/2017 05:40 PM, Paul Wouters wrote:
> 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.
>

You send me a signed email from a mutually trusted source. I now have 
your public key, because you can extract it from the signed S/MIME 
email. (I am guessing you can do this with PGP.)

I can now send you an encrypted email, and it includes my public key, so 
you can decrypt it.

There are free email cert companies. This email is signed by one (unless 
the list server strips them out like it used to). Your MUA now knows my 
public key.

-- 

Doug Royer - (http://DougRoyer.US  http://goo.gl/yrxJTu )
DouglasRoyer@gmail.com
714-989-6135