Skip to content

WPA-EAP-SHA256 + ieee80211w reported as WPA2 rather than WPA3 #8

@wryun

Description

@wryun

According to Section 3 of:
https://www.wi-fi.org/system/files/WPA3%20Specification%20v3.1.pdf

    wpa_key_mgmt=WPA-EAP WPA-EAP-SHA256
    ieee80211w=1
    => WPA3-Enterprise transition mode
    
    wpa_key_mgmt=WPA-EAP-SHA256
    ieee80211w=2
    => WPA3-Enterprise only mode

Also: openwrt/openwrt@b63df6c

However, iwinfo when looking at the hostapd conf file doesn't seem to think something is WPA3 until it gets to WPA-EAP-SHA384 (and doesn't consider the value of ieee80211w at all):

static const struct {
    const char *match;
    int version;
    int suite;
} wpa_key_mgmt_strings[] = {
    { "IEEE 802.1X/EAP", 0, IWINFO_KMGMT_8021x },
    { "EAP-SUITE-B-192", 4, IWINFO_KMGMT_8021x },
    { "EAP-SUITE-B",     4, IWINFO_KMGMT_8021x },
    { "EAP-SHA384",      4, IWINFO_KMGMT_8021x },
    { "EAP-SHA256",      0, IWINFO_KMGMT_8021x },
    { "PSK-SHA256",      0, IWINFO_KMGMT_PSK },
    { "NONE",            0, IWINFO_KMGMT_NONE },
    { "None",            0, IWINFO_KMGMT_NONE },
    { "PSK",             0, IWINFO_KMGMT_PSK },
    { "EAP",             0, IWINFO_KMGMT_8021x },
    { "SAE",             4, IWINFO_KMGMT_SAE },
    { "OWE",             4, IWINFO_KMGMT_OWE }
};

I'm also a bit surprised that iwinfo is even looking at the conf file rather than querying hostapd direclty (as it does with wpa_supplicant); not possible for some reason?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions