Re: [Emu] [Ace] About securing last exchange CoAP-EAP

Christian Amsüss <> Mon, 11 October 2021 10:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 65ECE3A09B8; Mon, 11 Oct 2021 03:16:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qH4aSwqcxe-I; Mon, 11 Oct 2021 03:16:10 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 274663A098B; Mon, 11 Oct 2021 03:16:09 -0700 (PDT)
Received: from (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by (Postfix) with ESMTPS id 0DEF6400D8; Mon, 11 Oct 2021 12:16:07 +0200 (CEST)
Received: from ( [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by (Postfix) with ESMTP id 1442C106; Mon, 11 Oct 2021 12:16:05 +0200 (CEST)
Received: from (unknown [IPv6:2a02:b18:c13b:8010:58a:38c7:d462:d25e]) by (Postfix) with ESMTPSA id BFC3510A; Mon, 11 Oct 2021 12:16:04 +0200 (CEST)
Received: (nullmailer pid 1456610 invoked by uid 1000); Mon, 11 Oct 2021 10:16:04 -0000
Date: Mon, 11 Oct 2021 12:16:04 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <>
To: Rafa Marin-Lopez <>
Cc: Dan Garcia Carrillo <>, EMU WG <>, "" <>
Message-ID: <>
References: <> <YRp7k/qFA0dE+/> <>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="gVxoZt2FxSxTitwa"
Content-Disposition: inline
In-Reply-To: <>
Archived-At: <>
Subject: Re: [Emu] [Ace] About securing last exchange CoAP-EAP
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 11 Oct 2021 10:16:16 -0000


sorry for spreading this out over the sub-threads[1], just to get the
pointers right and everything addressed:

On Fri, Sep 03, 2021 at 08:32:59PM +0200, Rafa Marin-Lopez wrote:
> 2) When the CoAP message contains the OSCORE ID that hits the OSCORE
>   context without any key material, we would have to assume this is
>   CoAP-EAP: the OSCORE implementation should not discard or give a
>   fail for this coap message but "pass the control" to CoAP-EAP so
>   that we send a altAccept to the EAP state machine so we get the MSK.

It's not because the context is without key material -- it's because
that context was created by EAP and that software component, rather than
giving a key, gave a "callback" (however it's precisely implemented)
that tells the OSCORE context to rather ask for a key with metadata from
the last message.

(OSCORE appendix B.2 needs something similar to implement, so this
shouldn't be new to OSCORE implementations).

> 3) From the MSK, we derive the OSCORE key material for the OSCORE
>   context with the corresponding ID and update the OSCORE context with
>   this key material 

The key IDs need to be preconfigured for this to work, see [2] -- but
that's best practice anyway.



To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom