Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correctly handle 64 hex digit passkey #1411

Merged
merged 2 commits into from
Oct 9, 2023
Merged

Correctly handle 64 hex digit passkey #1411

merged 2 commits into from
Oct 9, 2023

Conversation

billz
Copy link
Member

@billz billz commented Oct 8, 2023

A network defined in wpa_supplicant.conf may contain a passphrase, passkey or both. In cases where a known network exists with a valid 64-character passkey, but no passphrase, RaspAP will incorrectly throw a 'WPA passphrase must be between 8 and 63 characters' error.

Resolves #1397

# psk: WPA preshared key; 256-bit pre-shared key
# The key used in WPA-PSK mode can be entered either as 64 hex-digits, i.e.,
# 32 bytes or as an ASCII passphrase (in which case, the real PSK will be
# generated using the passphrase and SSID). ASCII passphrase must be between
# 8 and 63 characters (inclusive). ext:<name of external PSK field> format can
# be used to indicate that the PSK/passphrase is stored in external storage.

https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf

@billz billz merged commit 509af62 into master Oct 9, 2023
3 checks passed
@billz billz deleted the fix/wpa-passphrase branch October 9, 2023 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get erro "WPA passphrase must be between 8 and 63 characters" even when it is.
1 participant