Re: Why are mail servers not also key servers?

Paul Wouters <paul@nohats.ca> Thu, 20 April 2017 14:22 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 E5D2413146A for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 07:22:40 -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 6fUGXTvAhsY5 for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 07:22:25 -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 E72041296CF for <ietf@ietf.org>; Thu, 20 Apr 2017 07:22:24 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3w81KT3kJPzD49; Thu, 20 Apr 2017 16:22:21 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1492698141; bh=d8NRKWOMwQjidxEDAS/E5CaX8ewH78+E2NkqrOSoANc=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=heU3/qTRHtYpd34YXpe3MAjq4WYIpqSlM73VSwFoEvPHc7CCx1fGm6GEugmVpEDGk lW8UDi1IQKDJhXR4U08zQjsibZrwIE9DlZJlG5xPeUqX8SwaxAKsX6aC1WmYZJR7my MLJOYpEsxFAqYd3+GPCPP03FP92WCkcMl9ft6KPo=
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 8RcRlpervUQK; Thu, 20 Apr 2017 16:22:19 +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; Thu, 20 Apr 2017 16:22:19 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id C8C3F353643; Thu, 20 Apr 2017 10:22:17 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca C8C3F353643
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id C2A5840D811F; Thu, 20 Apr 2017 10:22:17 -0400 (EDT)
Date: Thu, 20 Apr 2017 10:22:17 -0400
From: Paul Wouters <paul@nohats.ca>
To: Jon <jmoroney@hawaii.edu>
cc: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
In-Reply-To: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
Message-ID: <alpine.LRH.2.20.999.1704201016120.518@bofh.nohats.ca>
References: <849511c0-6526-ecbe-2b56-7b459eaf010b@hawaii.edu>
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/SOgKu17cTRbpYG4ul6x7b9r4hYU>
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 14:22:41 -0000

On Thu, 20 Apr 2017, Jon wrote:

> Why are (E)SMTP servers not also key servers?

You will find a history of that discussion in the dane archives.

Basically, it is the equivalent to the domain's DNS servers acting as
key servers, except that:

- SMTP is often blocked cross-domain, eg by ISPs, hotspot operators, etc
- SMTP failure cannot be distinguished from SMTP attacks, whereas DNSSEC
   based published keys (eg OPENPGPKEY and SMIMEA) can be detected when
   blocked (DNSSEC returns bogus or indeterminate results)
- Using public DNS to publish keys allows for a level of indirection,
   making targeted attacks much harder to do.

> generate a key pair on registration, store those keys on the server (in
> an encrypted archive), and make the public key available. A little
> coding later and we've got key exchange and message confidentiality.

SMTP servers could be key servers without having the private key of
individuals?

> Some extra security can be had by giving mail servers their own keys
> with which they can sign exchanges (and remember each other). TLS can be
> used to as part of an initial key exchange if that is desired. Can
> we not extend smtp again to include the necessary key exchange commands?

I believe there was a draft that tried to do something like this.

Paul