IETF Logo Mail Archive

Re: [saag] Perfect Forward Secrecy vs Forward Secrecy

Robert Moskowitz <rgm-sec@htt-consult.com> Mon, 23 March 2020 17:57 UTC

Return-Path: <rgm-sec@htt-consult.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7C243A0E1E for <saag@ietfa.amsl.com>; Mon, 23 Mar 2020 10:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 LcpSsCCLavv9 for <saag@ietfa.amsl.com>; Mon, 23 Mar 2020 10:57:45 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B22A93A0E33 for <saag@ietf.org>; Mon, 23 Mar 2020 10:57:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 5398F62145; Mon, 23 Mar 2020 13:57:44 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id YP-SdXBPam6I; Mon, 23 Mar 2020 13:57:39 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 82E5D6212E; Mon, 23 Mar 2020 13:57:39 -0400 (EDT)
To: Benjamin Kaduk <kaduk@mit.edu>, saag@ietf.org
References: <7231a98e-e4a2-55c9-3a51-d62886d7d061@htt-consult.com> <BAFBB844-0AB4-41A5-9A15-B9CED6F6602C@icloud.com> <20200323011940.GI50174@kduck.mit.edu>
From: Robert Moskowitz <rgm-sec@htt-consult.com>
Message-ID: <117849db-3b7a-d0ec-ccf7-7315e935a13b@htt-consult.com>
Date: Mon, 23 Mar 2020 13:57:26 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <20200323011940.GI50174@kduck.mit.edu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/8boMIxMToLQsZgcjLwlyl82wQ5Y>
Subject: Re: [saag] Perfect Forward Secrecy vs Forward Secrecy
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2020 17:58:13 -0000


On 3/22/20 9:19 PM, Benjamin Kaduk wrote:
> On Wed, Mar 18, 2020 at 09:38:07AM -0700, Jon Callas wrote:
>> We don't do "perfect" security in our fundamentals, because, as the unnamed AD said, it's hard to achieve.
> For what little it's worth, the AD doesn't have to be unnamed; I'm happy to
> own up to making the request of Bob.  I just haven't gotten fully caught up
> on mail yet.

And draft 17 reflects this view of Forward Secrecy.

Thanks, Ben.

v2.23.0 | Report a Bug | By Email