Unclear/misleading documentation for /etc/network/interfaces extensions
Bug #44315 reported by
Niku Toivola
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| wpasupplicant (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: wpasupplicant
The wpa_supplicant provided extensions to /etc/network/
1. Add these extensions to the wpa_supplicant man page (or some other suitable man page) and add a pointer to that in the interfaces(5) man page, similar to the wireless extensions and wireless(7).
2. Clarify the documentation for wpa-psk and wpa-passphrase so that the functionality is clear: 'wpa-psk "ascii passphrase in quotes"' works, 'wpa-psk <psk in hex format>' works, 'wpa-passphrase ascii passphrase without quotes' works, 'wpa-passphrase "ascii passphrase in quotes"' mysteriously fails.
Revision history for this message
| kelmo (kelrin) wrote | #1 |
Revision history for this message
| Reinhard Tartler (siretart) wrote | #2 |
Revision history for this message
| Reinhard Tartler (siretart) wrote | #3 |
| Changed in wpasupplicant: | |
| status: | Unconfirmed → Fix Released |
To post a comment you must log in.
I hope that recent changes in debians 0.5.5-2 wpasupplicant version address this issue.
In that version the 'wpa-psk' value is evaluated as follows:
It is considered to be 256-bit hex key when containing exactly 64 hexadecimal only characters, otherwise it is considered as a passphrase. There is no need for quoted passphrases or 'wpa-passphrase' in this case (but remains compat. with those mentioned cases).
This makes the documentation much more simple, and less obsfucated for the end user.
What do others think about patching interfaces(5) manpage to add reference to wpasupplicant stuff?