Hi Alexander,
We will update the implementation and clarify the use of channel binding
in EAP-EDHOC in the next version of the draft.
Thank you.
Best regards,
Dan.
El 15/7/25 a las 7:37, Alexander Clouter escribió:
Hello,
On Mon, 14 Jul 2025, at 10:28, FRANCISCO LOPEZ GOMEZ wrote:
Our implementation (University of Murcia) is available and can be
tested at:
https://urldefense.com/v3/__https://gitlab.com/franciscolopezg/eap-edhoc-testbed.git__;!!D9dNQwwGXtA!XlJGMVKC6lUMqN1jh1yvApF1s0VHOR2EiFPImMZZr7Q9f0m_gbYXep9CWIwlQwYuRRj_-SV_7hMzO8obvKFYS9lsEE3dxeKC$
.
This repository includes some proof-of-concept implementations of the
EAP-EDHOC method, a Dockerized test environment, and instructions to
reproduce the tests.
Maybe important, the implementation[1] was made using
draft-ietf-emu-eap-edhoc-00 and since then the channel-binding section was
added.
Can anyone chip in and state if the channel binding with validation was ever
implemented anywhere?
The draft states "the channel binding protocol defined in [RFC6677] must be
transported after keying material" without anything material (to me) on how to
actually go an do this as an implementer.
For example what is the actual process in doing "If the server detects a consistency
error in the channel binding information contained in EAD_3" and how does a peer
respond if it is upset?
Cheers
Alex
[1]
https://urldefense.com/v3/__https://gitlab.com/franciscolopezg/eap-edhoc-testbed/-/blob/main/base/freeradius-server-3.2.3/src/modules/rlm_eap/types/rlm_eap_edhoc/eap_edhoc.h?ref_type=heads__;!!D9dNQwwGXtA!XlJGMVKC6lUMqN1jh1yvApF1s0VHOR2EiFPImMZZr7Q9f0m_gbYXep9CWIwlQwYuRRj_-SV_7hMzO8obvKFYS9lsEJnsW8ZG$
_______________________________________________
Emu mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
Emu mailing list -- [email protected]
To unsubscribe send an email to [email protected]
