Re: On email and web security

"John Levine" <> Thu, 31 December 2015 19:37 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id D8BD81A8A6B for <>; Thu, 31 Dec 2015 11:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.663
X-Spam-Level: *
X-Spam-Status: No, score=1.663 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2iSCWBCQ9O8b for <>; Thu, 31 Dec 2015 11:37:44 -0800 (PST)
Received: from ( [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7AC791A8A59 for <>; Thu, 31 Dec 2015 11:37:44 -0800 (PST)
Received: (qmail 8891 invoked from network); 31 Dec 2015 19:37:43 -0000
Received: from unknown ( by with QMQP; 31 Dec 2015 19:37:43 -0000
Date: Thu, 31 Dec 2015 19:37:21 -0000
Message-ID: <20151231193721.1139.qmail@ary.lan>
From: John Levine <>
Subject: Re: On email and web security
In-Reply-To: <>
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 31 Dec 2015 19:37:46 -0000

>Second, many of my colleagues have asked me to remove their old keys from my database, because they
>have forgotten them, although the PGP repository has not.

FWIW, the public repository at reverifies the keys from time
to time.  Earlier this week I got a couple of messages saying that if
I still wanted them to publish keys corresponding to those addresses,
click through and reconfirm.  (Yes, I realize how weak this is, but
in the circumstances it's better than nothing.)

Your overall point that the problem with crypto is that it's unusable
if you're not a hard core geek is of course correct.

>Third, I note that when I receive a signed email that has gone through an IETF alias, I can no longer
>verify the signature as a result of content modification. What is the value of a signature one cannot

With the advent of DMARC, this problem now affects a lot more people
than ones who are looking for PGP signatures.