diff options
author | Nick Lowe <nick.lowe@gmail.com> | 2022-02-21 17:51:48 +0000 |
---|---|---|
committer | Paul Spooren <mail@aparcar.org> | 2022-02-24 18:04:05 +0100 |
commit | e8d048c5e0ad0807a0362fe31c68c8f5eb228bff (patch) | |
tree | 0f56985f1680061c6ee81bf0fca89301f07f3862 /package/network/services/ipset-dns/Makefile | |
parent | fb5d0dc362e5206dbedb694dbe27953582eb887b (diff) | |
download | upstream-e8d048c5e0ad0807a0362fe31c68c8f5eb228bff.tar.gz upstream-e8d048c5e0ad0807a0362fe31c68c8f5eb228bff.tar.bz2 upstream-e8d048c5e0ad0807a0362fe31c68c8f5eb228bff.zip |
hostapd: SAE - Enable hunting-and-pecking and H2E
Enable both the hunting-and-pecking loop and hash-to-element mechanisms
by default in OpenWRT with SAE.
Commercial Wi-Fi solutions increasingly frequently now ship with both
hunting-and-pecking and hash-to-element (H2E) enabled by default as this
is more secure and more performant than offering hunting-and-pecking
alone for H2E capable clients.
The hunting and pecking loop mechanism is inherently fragile and prone to
timing-based side channels in its design and is more computationally
intensive to perform. Hash-to-element (H2E) is its long-term
replacement to address these concerns.
For clients that only support the hunting-and-pecking loop mechanism,
this is still available to use by default.
For clients that in addition support, or were to require, the
hash-to-element (H2E) mechanism, this is then available for use.
Signed-off-by: Nick Lowe <nick.lowe@gmail.com>
Diffstat (limited to 'package/network/services/ipset-dns/Makefile')
0 files changed, 0 insertions, 0 deletions