Re: DEADBEEF vs SHA1

David Shaw <dshaw@jabberwocky.com> Fri, 18 February 2011 21:07 UTC

Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (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 owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p1IL755J093058; Fri, 18 Feb 2011 14:07:05 -0700 (MST) (envelope-from owner-ietf-openpgp@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from walrus.jabberwocky.com (walrus.jabberwocky.com [173.9.29.57]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p1IL738g093046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-openpgp@imc.org>; Fri, 18 Feb 2011 14:07:04 -0700 (MST) (envelope-from dshaw@jabberwocky.com)
Received: from dshaw.nasuni.net (gw-comcast1.nasuni.com [173.166.63.186]) (authenticated bits=0) by walrus.jabberwocky.com (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 <dshaw@jabberwocky.com>
In-Reply-To: <C997753D-9BB7-445C-A95C-260B3BE11F78@callas.org>
Date: Fri, 18 Feb 2011 16:06:59 -0500
Cc: IETF OpenPGP Working Group <ietf-openpgp@imc.org>
Message-Id: <E6B0382E-B9D9-4DCC-8027-9DFE91B4C75D@jabberwocky.com>
References: <D8E81788-AF18-448F-BA39-56185C1F0672@jabberwocky.com> <4D5DB5A9.9040509@iang.org> <315DE4B7-F5C7-4FA6-9A0F-2CAD305D4DF2@jabberwocky.com> <C997753D-9BB7-445C-A95C-260B3BE11F78@callas.org>
To: Jon Callas <jon@callas.org>
X-Mailer: Apple Mail (2.1081)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by hoffman.proper.com id p1IL748f093054
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>

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").

David