Re: [lamps] Adam Roach's Comment on draft-ietf-lamps-cms-mix-with-psk-06

Adam Roach <adam@nostrum.com> Wed, 21 August 2019 21:32 UTC

Return-Path: <adam@nostrum.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E73B12001E; Wed, 21 Aug 2019 14:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level:
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.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 O3o6X1TwzVdY; Wed, 21 Aug 2019 14:31:58 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F8DB120098; Wed, 21 Aug 2019 14:31:58 -0700 (PDT)
Received: from MacBook-Pro.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id x7LLVttx002962 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 21 Aug 2019 16:31:57 -0500 (CDT) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1566423118; bh=zh8pScHkB5i0fpdxbA5KZ7id/Fh7aVZbgvfpcaaDPVc=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=KaVYVkRUVTj72g/YGESwnv7f1Ap1tCMZj+0QT5DDTM0XVXQZsfJmgrIxO/8g3q49g KsDS0Upb9WmrL0e/etiYZ2x6L/Sa91uelL9/YnjZBudO59+D751wttLc21bvb4HAi6 JDe+MUhOH+nf3zlfviwVhGogNwaQyHrAOeomhXXo=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be MacBook-Pro.roach.at
To: Russ Housley <housley@vigilsec.com>
Cc: IESG <iesg@ietf.org>, LAMPS WG <spasm@ietf.org>
References: <38527132-0951-49CF-A043-A39B206BB0B7@vigilsec.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <9fadacdf-0b0b-5a52-a335-9287743ede59@nostrum.com>
Date: Wed, 21 Aug 2019 16:31:50 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <38527132-0951-49CF-A043-A39B206BB0B7@vigilsec.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/kKTbV599QEIP-rABeJwRTQmalyc>
Subject: Re: [lamps] Adam Roach's Comment on draft-ietf-lamps-cms-mix-with-psk-06
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Aug 2019 21:32:02 -0000

On 8/21/19 3:57 PM, Russ Housley wrote:
> Adam:
>
> I was looking for something else and I stumbled across your COMMENT on draft-ietf-lamps-cms-mix-with-psk-06.
>
>> Thanks for the work on this document. It seems like a useful tool
>> to add to the crypto toolkit, and it does a good job of explaining
>> exactly how to apply the described technique. I have one minor
>> comment.
>>
>> §7:
>>
>> I don't generally have a deep understanding of the math behind
>> encryption, and I didn't take the time to really align the technique
>> in this document with the bit of crypto that I do understand, so
>> forgive me if this is a naive observation: I was somewhat surprised
>> to see no text in here regarding the advisability (or lack thereof)
>> regarding re-use of PSKs across different sessions.
>
> I suggest this additional sentence to Section 2 to address your comment:
>
>     A PSK is expected to be used with many messages, with a
>     lifetime of weeks or months.


Yep, that sounds good to me. Thanks!

/a