From 08fcb0e8fba4ef1dc770253bfbb330fa0c02e096 Mon Sep 17 00:00:00 2001 From: Michael Brown Date: Wed, 10 Jan 2024 15:23:07 +0000 Subject: [eap] Add support for the MD5-Challenge authentication type RFC 3748 states that support for MD5-Challenge is mandatory for EAP implementations. The MD5 and CHAP code is already included in the default build since it is required by iSCSI, and so this does not substantially increase the binary size. Signed-off-by: Michael Brown --- src/include/ipxe/eap.h | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'src/include/ipxe') diff --git a/src/include/ipxe/eap.h b/src/include/ipxe/eap.h index bbae517da..cf1c7c00d 100644 --- a/src/include/ipxe/eap.h +++ b/src/include/ipxe/eap.h @@ -49,6 +49,17 @@ struct eap_message { /** EAP NAK */ #define EAP_TYPE_NAK 3 +/** EAP MD5 challenge request/response */ +#define EAP_TYPE_MD5 4 + +/** EAP MD5 challenge request/response type data */ +struct eap_md5 { + /** Value length */ + uint8_t len; + /** Value */ + uint8_t value[0]; +} __attribute__ (( packed )); + /** EAP success */ #define EAP_CODE_SUCCESS 3 -- cgit v1.2.3-55-g7522