David Shaw <> Fri, 18 February 2011 21:07 UTC

Received: from (localhost []) by (8.14.4/8.14.3) with ESMTP id p1IL75Q9093059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Feb 2011 14:07:05 -0700 (MST) (envelope-from
Received: (from majordom@localhost) by (8.14.4/8.13.5/Submit) id p1IL755J093058; Fri, 18 Feb 2011 14:07:05 -0700 (MST) (envelope-from
X-Authentication-Warning: majordom set sender to using -f
Received: from ( []) by (8.14.4/8.14.3) with ESMTP id p1IL738g093046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <>; Fri, 18 Feb 2011 14:07:04 -0700 (MST) (envelope-from
Received: from ( []) (authenticated bits=0) by (8.14.4/8.14.4) with ESMTP id p1IL6xPN012947 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 18 Feb 2011 16:07:00 -0500
Subject: Re: DEADBEEF vs SHA1
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: David Shaw <>
In-Reply-To: <>
Date: Fri, 18 Feb 2011 16:06:59 -0500
Cc: IETF OpenPGP Working Group <>
Message-Id: <>
References: <> <> <> <>
To: Jon Callas <>
X-Mailer: Apple Mail (2.1081)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by id p1IL748f093054
Precedence: bulk
List-Archive: <>
List-Unsubscribe: <>
List-ID: <>

On Feb 18, 2011, at 1:29 PM, Jon Callas wrote:

> There are a number of ways to deal with this. For example, I could have a copy of PGP 2.6.3 lying around and use that to decrypt my old things. That's only a mild inconvenience. Similarly, PGP or GnuPG could keep v3 keys around *as* *software* for such archival purposes. It might even make sense from a user experience aspect to have them in historic keyrings that are not in one's face every day.

Right, a historic keyring is the sort of thing I'm envisioning, along with some sort of application knob to use it ("click here to enable V3 keys" or "--enable-v3-keys") or not ("--disable-v3-keys").