IETF Logo Mail Archive

Re: [openpgp] email death certificates

Michael Richardson <mcr@sandelman.ca> Wed, 28 August 2019 00:29 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5F4B120026 for <openpgp@ietfa.amsl.com>; Tue, 27 Aug 2019 17:29:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 xGXLq8LcPyYT for <openpgp@ietfa.amsl.com>; Tue, 27 Aug 2019 17:29:26 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0577D12009E for <openpgp@ietf.org>; Tue, 27 Aug 2019 17:29:25 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 069AE3818C; Tue, 27 Aug 2019 20:28:16 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 274D889; Tue, 27 Aug 2019 20:29:24 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Jon Callas <joncallas@icloud.com>
cc: openpgp@ietf.org
In-Reply-To: <1AEEDBA4-B3D8-4356-8904-E1407C7AA4EA@icloud.com>
References: <5409.1566583500@dooku.sandelman.ca> <1AEEDBA4-B3D8-4356-8904-E1407C7AA4EA@icloud.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 27 Aug 2019 20:29:24 -0400
Message-ID: <21145.1566952164@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/e2larvzS8WR8gINgdz9Tnbc4rXY>
Subject: Re: [openpgp] email death certificates
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Aug 2019 00:29:28 -0000

Jon Callas <joncallas@icloud.com> wrote:
    >> On Aug 23, 2019, at 11:05 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
    >> 
    >> Has anyone given any thought to this?
    >> 
    >> I suppose it might also apply to "does not work here anymore"

    > Yes, as others have said, designated revokers and reason-for-revocation
    > are part of this, as would be even human-readable notations.  

    > In PGP, we had key-splitting and those one could with that product
    > key-split a revoker key. It was an obvious use case for us, even.

The designated revoker seems to require advance planning, as does the
key-splitting.   People rarely do advance planing on accidential death, nor
on getting fired.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email