Re: Why are mail servers not also key servers?

Doug Royer <douglasroyer@gmail.com> Thu, 20 April 2017 17:56 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 5E1DB131493 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-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 HiMy9lTaCrCw for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 10:56:12 -0700 (PDT)
Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (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 68494129B74 for <ietf@ietf.org>; Thu, 20 Apr 2017 10:56:12 -0700 (PDT)
Received: by mail-oi0-x242.google.com with SMTP id y11so9783806oie.1 for <ietf@ietf.org>; Thu, 20 Apr 2017 10:56:12 -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=itdhqU8BuFAmDrRWf9VPp9H3igimZLlyBSmB8Q7VR0M=; b=V52YFuvpZCDb9Yhs9AFPLu0K1mWVCyTqlVXTLNEcU9N9vo1KlmVnOFdK8Wyz+BExir xeplvxhTPMAtiknB2dTC1Ql91d6GHJJiECxuFxgooGBshjWAX5bra6EralA/SdlFHz/m UuUngr8eThkMrEyfUezygo4nlgNNOdOTD7nxZ42DtQWmEjT6Wn3nex63MNwcpZ68RYns P2GgQtdHW0eCMgrFz8hrHzrkx74aAsCQKcw3eAGvPR53Nvb/ZBL1/7RcoQ0ujjctXEjK wiDx2x1kglQ5PfAPsdWzRO9VCi1vpj7c7NoTZABJjTVrWgq+ZBpPaCyLVf3xH7ZSSFMb 1ivw==
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=itdhqU8BuFAmDrRWf9VPp9H3igimZLlyBSmB8Q7VR0M=; b=eoMh/5WUJk7wnUKxcUYz+IG3vGSgOOW++c0kISh4cnB0xR+YRusY1dQOdDZ08xZ/rv 41U4DFXUu081jamb1guFKkyKBFVXoDhLYSDK2QhZ5b21Lh6FZ2qJiDa28Om9L+bp62qC T1nIHKincVVRGn8LjlJpRiZJBGjqV6SGLvqmIpZLvFUYRf76yjKc4gMxUoImxamCm6QS ep6iGvVyxS7rbMFsg+wqxt5q2NGUyVqzx/doW4TqjlfazBY3Q+Fq7Kl4JHEfDTygp8ra 0zbUjHF5CjzrsYBYnRp7a027y1Sewx/mFIzvzeUZPK+/wXy8YKx7JJx2mWrxvNRZLEa6 5D8g==
X-Gm-Message-State: AN3rC/7LF5QsxOwVHysjcIT4iJOKM5YU8z5NR2nczm0t6zLCmrYMtXjQ 7b+TrxoqizqI+KrXv0U=
X-Received: by 10.202.50.131 with SMTP id y125mr5147844oiy.105.1492710971433; Thu, 20 Apr 2017 10:56:11 -0700 (PDT)
Received: from ?IPv6:2602:ae:1b37:7300::2? ([2602:ae:1b37:7300::2]) by smtp.googlemail.com with ESMTPSA id j17sm2826222ota.24.2017.04.20.10.56.09 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Apr 2017 10:56:10 -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>
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
Message-ID: <f5149504-12a1-728b-e685-3f75be6869c1@gmail.com>
Date: Thu, 20 Apr 2017 11:56:08 -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: <20170420173551.GN25754@mournblade.imrryr.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms060905080803040705000203"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/en1FftYSAS6qmSvnB4NBa-WjlkI>
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 17:56:14 -0000

On 04/20/2017 11:35 AM, Viktor Dukhovni wrote:
> On Thu, Apr 20, 2017 at 07:01:05PM +0200, Jon wrote:
> 
>> This is why I think smtp should be extended. All your mail agents
>> support (E)SMTP and presumably they would all support an extension to
>> smtp. The private keys will need to be stored some how to allow for
>> multiple clients, but a key generated from user input could be used to
>> decrypt a stored copy of the private key.
> 
> A major problems with all E2E email encryption proposals is unrelated
> to key distribution, none of the extant MUAs provide an adequate
> interface for E2E encrypted email.
> 
>        + Encrypted email is not searchable.

Sure it is, by the recipient MUA, else the user could not read their 
email. It would not be searchable by a 3rd party - which is the point of 
encryption.

>        + Encrypted email is difficult to scan for spam and malware

The scan would have to take place in the MUA. Firewall scanners would 
fail, as they do now with S/MIME or encrypted PGP.

>        + Changing the private key can mean loss of access to email
> 	encrypted under the old key.

Only if you throw away old keys. Doctor, Doctor, it hurts when I do 
this. - So Do not do that :-)

>        + Signatures stop verifying when the signature key expires,
> 	even though they were valid at the the email was received.

Again, do not throw away the old keys. An MUA should not allow a user to 
throw away any key needed for any message still in the store. Yep - complex.

> ....

-- 

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