Re: [openpgp] email death certificates
"Derek Atkins" <derek@ihtfp.com> Fri, 23 August 2019 18:08 UTC
Return-Path: <derek@ihtfp.com>
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 5FCF712006A for <openpgp@ietfa.amsl.com>; Fri, 23 Aug 2019 11:08:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ihtfp.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 yukUGEel-OBZ for <openpgp@ietfa.amsl.com>; Fri, 23 Aug 2019 11:08:19 -0700 (PDT)
Received: from mail2.ihtfp.org (MAIL2.IHTFP.ORG [204.107.200.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4917F120044 for <openpgp@ietf.org>; Fri, 23 Aug 2019 11:08:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 817E7E2045; Fri, 23 Aug 2019 14:08:15 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 15008-06; Fri, 23 Aug 2019 14:08:13 -0400 (EDT)
Received: by mail2.ihtfp.org (Postfix, from userid 48) id 83BA0E2044; Fri, 23 Aug 2019 14:08:13 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1566583693; bh=+pzzG/xpatEjBDPTMGPS/yjwa/jqrMkbG1GTEcUJkyc=; h=In-Reply-To:References:Date:Subject:From:To:Cc; b=ZS+IzN2HyVkfz+mJMf5vwWMW0csYitOzcDeGmTfU4xh50MRPknQyvECRMSv+mZepF MOquoFZEYbmAoVrD/nv8RUGHnGg3778ZFp1a5hRUcVkwTIVRje6zbE0Wn7aMawYiP4 bljupmDi1+56PaA64h+9S8ItwXAME8gatbROIgNo=
Received: from 169.231.97.194 (SquirrelMail authenticated user warlord) by mail2.ihtfp.org with HTTP; Fri, 23 Aug 2019 14:08:13 -0400
Message-ID: <9b0c6fddc26bc1480292cd880ec48e69.squirrel@mail2.ihtfp.org>
In-Reply-To: <5409.1566583500@dooku.sandelman.ca>
References: <5409.1566583500@dooku.sandelman.ca>
Date: Fri, 23 Aug 2019 14:08:13 -0400
From: Derek Atkins <derek@ihtfp.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: openpgp@ietf.org
User-Agent: SquirrelMail/1.4.22-14.fc20
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/uHHq0IPNTGwMnrK5QEivar4ZLck>
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: Fri, 23 Aug 2019 18:08:22 -0000
There is the "designated revoker" feature? Not sure offhand if there are reason-codes. -derek On Fri, August 23, 2019 2:05 pm, Michael Richardson wrote: > > I had the unfortunate duty to remove an email address from a community > email list because the person had passed away. I wonder how many other > lists this rather active person is on, and how many years it will be > before the lists are cleaned up. > > When my dad passed away in the fall of 2003, it wasn't until the end of > April > the following year that the University cleaned up his email account. > There > was clearly a need to keep the account open for quite some time due to > other university business that hadn't yet closed. > > I was thinking this morning about an SMTP responses, a 55x-type, > but it rather needs to be signed. Sigh, 2019, and still not enough > useful email security to do this. But still. > > Is there something in openpgp spec that I'm missing here? > I don't think that revoking the key is the right thing. > In particular, nobody may know how to find the private key to revoke it. > What's wanted is a revocation of the PGP signature with a reason. > > Has anyone given any thought to this? > > I suppose it might also apply to "does not work here anymore" > > -- > Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works > -= IPv6 IoT consulting =- > > > > _______________________________________________ > openpgp mailing list > openpgp@ietf.org > https://www.ietf.org/mailman/listinfo/openpgp > -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant
- [openpgp] email death certificates Michael Richardson
- Re: [openpgp] email death certificates Derek Atkins
- Re: [openpgp] email death certificates David Shaw
- Re: [openpgp] email death certificates Stephen Farrell
- Re: [openpgp] email death certificates Michael Richardson
- Re: [openpgp] email death certificates Peter Gutmann
- Re: [openpgp] email death certificates David Shaw
- Re: [openpgp] email death certificates Heiko Stamer
- Re: [openpgp] email death certificates Jon Callas
- Re: [openpgp] email death certificates Michael Richardson
- Re: [openpgp] email death certificates Jon Callas