IETF Logo Mail Archive

Re: V3 secret keys

nagydani@epointsystem.org (Daniel A. Nagy) Thu, 02 February 2006 14:21 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F4fLH-0005rr-Es for openpgp-archive@megatron.ietf.org; Thu, 02 Feb 2006 09:21:59 -0500
Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06812 for <openpgp-archive@lists.ietf.org>; Thu, 2 Feb 2006 09:19:53 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id k12E6IeF044875; Thu, 2 Feb 2006 06:06:18 -0800 (PST) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id k12E6Iid044871; Thu, 2 Feb 2006 06:06:18 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from mail.epointsystem.org ([195.228.156.120]) by above.proper.com (8.12.11/8.12.9) with ESMTP id k12E6D8e044853 for <ietf-openpgp@imc.org>; Thu, 2 Feb 2006 06:06:16 -0800 (PST) (envelope-from nagydani@epointsystem.org)
Received: by mail.epointsystem.org (Postfix, from userid 1001) id 81D8E2B45D2; Thu, 2 Feb 2006 15:06:12 +0100 (CET)
Date: Thu, 02 Feb 2006 15:06:12 +0100
To: Ben Laurie <ben@algroup.co.uk>
Cc: OpenPGP <ietf-openpgp@imc.org>
Subject: Re: V3 secret keys
Message-ID: <20060202140612.GA13906@epointsystem.org>
References: <43E20DB6.30209@algroup.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <43E20DB6.30209@algroup.co.uk>
User-Agent: Mutt/1.5.6+20040907i
From: nagydani@epointsystem.org
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 Thu, Feb 02, 2006 at 01:48:38PM +0000, Ben Laurie wrote:
> 
> in 5.5.3 it says:
> 
> "Furthermore, the CFB state is resynchronized at the beginning of each
> new MPI value,  so that the CFB block boundary is aligned with the start
> of the MPI data."
> 
> I can't find anywhere a precise (or even an imprecise) definition of
> "resynchronized". What exactly does it mean?
> 
> Does it mean that the IV is reset to whatever it was at the start of the
> current block? Does it mean that we use the partially-updated IV, but
> set the position back to the beginning? Does it mean we reset the IV to
> the initial value and start again? Or what?
> 
> Cheers,
> 
> Ben.

It means the usual CFB synchronization with outputting a partial block and
shifting the IV.

-- 
Daniel

v2.23.0 | Report a Bug | By Email