IETF Logo Mail Archive

Re: Why are mail servers not also key servers?

Paul Wouters <paul@nohats.ca> Thu, 20 April 2017 20:11 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 3A4AE129C1A for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 13:11:32 -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 1LTnaHdX7HXG for <ietf@ietfa.amsl.com>; Thu, 20 Apr 2017 13:11:30 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.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 693681293F2 for <ietf@ietf.org>; Thu, 20 Apr 2017 13:11:30 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3w894J54ldzDH9; Thu, 20 Apr 2017 22:11:28 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1492719088; bh=bsHQ17iuNKR22a5bOYBuSEMB6TmwCEIWWJisKIHWzNY=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=IdHGbr7Lat+QVxLWTQugl0e2xYISLdDhwzVYMMNAD3swvpikf7VNC6Ca8SLjVfb3v 8OWYLrgleG8SJijVqH1BXTxTpXZAv3z3TgLtaw8eiafrv2ZEC4I1uBphtHE+ofhkqS UY/mV4e0l9NTaCcStfUxSAOGOf2I02thLGf3fi+0=
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 ZiVKbep4seoD; Thu, 20 Apr 2017 22:11:27 +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 22:11:27 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id EF405418565; Thu, 20 Apr 2017 16:11:26 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca EF405418565
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id EA27B40B7F47; Thu, 20 Apr 2017 16:11:26 -0400 (EDT)
Date: Thu, 20 Apr 2017 16:11:26 -0400
From: Paul Wouters <paul@nohats.ca>
To: Nico Williams <nico@cryptonector.com>
cc: ietf@ietf.org
Subject: Re: Why are mail servers not also key servers?
In-Reply-To: <20170420192604.GF2856@localhost>
Message-ID: <alpine.LRH.2.20.999.1704201608320.13482@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>
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/o6At8IFtjti1mWhPbdJvuErf9L8>
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 20:11:32 -0000

On Thu, 20 Apr 2017, Nico Williams wrote:

> Part of the problem is that there is very little work being done on
> MUAs.

I think there is just no work to be done. Decrypt the email on the MUA
and store/use it as any uncrypted email now and run the OS or at least
the user's directory using a disk encryption system.

Paul

v2.23.0 | Report a Bug | By Email