path: root/src/wps/wps_dev_attr.h
Commit message (Collapse)AuthorAgeFilesLines
* WPS: Add application extension data to WPS IEBilal Hatipoglu2020-01-041-0/+1
| | | | | | | | | | | | | | Application Extension attribute is defined in WSC tech spec v2.07 page 104. Allow hostapd to be configured to add this extension into WPS IE in Beacon and Probe Response frames. The implementation is very similar to vendor extension. A new optional entry called "wps_application_ext" is added to hostapd config file to configure this. It enodes the payload of the Application Extension attribute in hexdump format. Signed-off-by: Veli Demirel <veli.demirel@airties.com> Signed-off-by: Bilal Hatipoglu <bilal.hatipoglu@airties.com>
* hostapd: Support Multi-AP backhaul STA onboarding with WPSDavina Lu2019-02-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Wi-Fi Alliance Multi-AP Specification v1.0 allows onboarding of a backhaul STA through WPS. To enable this, the WPS Registrar offers a different set of credentials (backhaul credentials instead of fronthaul credentials) when the Multi-AP subelement is present in the WFA vendor extension element of the WSC M1 message. Add new configuration options to specify the backhaul credentials for the hostapd internal registrar: multi_ap_backhaul_ssid, multi_ap_backhaul_wpa_psk, multi_ap_backhaul_wpa_passphrase. These are only relevant for a fronthaul SSID, i.e., where multi_ap is set to 2 or 3. When these options are set, pass the backhaul credentials instead of the normal credentials when the Multi-AP subelement is present. Ignore the Multi-AP subelement if the backhaul config options are not set. Note that for an SSID which is fronthaul and backhaul at the same time (i.e., multi_ap == 3), this results in the correct credentials being sent anyway. The security to be used for the backaul BSS is fixed to WPA2PSK. The Multi-AP Specification only allows Open and WPA2PSK networks to be configured. Although not stated explicitly, the backhaul link is intended to be always encrypted, hence WPA2PSK. To build the credentials, the credential-building code is essentially copied and simplified. Indeed, the backhaul credentials are always WPA2PSK and never use per-device PSK. All the options set for the fronthaul BSS WPS are simply ignored. Signed-off-by: Davina Lu <ylu@quantenna.com> Signed-off-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Marianna Carrera <marianna.carrera.so@quantenna.com>
* P2P NFC: Add WPS attribute building for P2P NFCJouni Malinen2014-01-271-0/+1
| | | | | | | These functions can be used to build the WPS attributes for P2P NFC connection handover messages. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Remove unused wps_device_data_dup()Jouni Malinen2013-12-291-2/+0
| | | | Signed-hostap: Jouni Malinen <j@w1.fi>
* WPS: Set currently used RF band in RF Bands attributeDavid Spinadel2013-08-251-1/+2
| | | | | | | | | According to WSC specification (Ver 2.0.2, section 8.3), RF Bands attribute should be set to the specific RF band used for the current message. Add an option to set wanted band in wps_build_rf_bands() and add a callback to get the current band from wpa_supplicant and hostapd. Signed-hostap: David Spinadel <david.spinadel@intel.com>
* WPS: Allow vendor specific attribute to be added into M1Anirban Sirkhell2012-04-031-0/+1
| | | | | | | | wps_vendor_ext_m1 configuration parameter can now be used to add a vendor specific attribute into the WPS M1 message, e.g., for Windows Vertical Pairing. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
* Remove the GPL notification from files contributed by Jouni MalinenJouni Malinen2012-02-111-8/+2
| | | | | | | Remove the GPL notification text from the files that were initially contributed by myself. Signed-hostap: Jouni Malinen <j@w1.fi>
* P2P: Add option for requested device type in P2P search/scanJean-Michel Bachot2011-03-191-0/+3
| | | | | | | With this, p2p_find can be extended to find certain requested device types. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
* WPS: Add support for adding WPS Vendor ExtensionsJean-Michel Bachot2011-03-191-0/+1
| | | | | | | This adds the ability to add WPS vendor extensions to an AP (or GO). They will be added to the WSC IE(s) in Beacon and Probe Response frames. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
* WPS: Add secondary device types into Probe Request framesJean-Michel Bachot2011-03-171-0/+2
| | | | | | | The secondary device type list is an optional attribute in the WSC IE. Signed-off-by: Jean-Michel Bachot <jean-michelx.bachot@linux.intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
* P2P: Add Device Name into WPS IE in Probe Request framesJouni Malinen2010-09-091-0/+1
* WPS 2.0: Add device attributes into Probe RequestJouni Malinen2010-09-091-0/+4
| | | | | Add Manufacturer, Model Name, Model Number, and Device Name attributes into the WSC IE in the Probe Request frames.
* WPS: Moved RF Bands processing into wps_dev_attr.cJouni Malinen2008-11-291-0/+2
| | | | This allows the RF Bands attribute to be configured and stored.
* WPS: Moved device attributes into wps_context::dev for Enrollee caseJouni Malinen2008-11-281-0/+2
| | | | | | | | | | Previously, hardcoded values were used in wps_enrollee.c. These are now moved into shared data in struct wps_context. In case of AP/Authenticator, these are initialized in wps_hostapd.c. In case of client/supplicant, these are now initialized in EAP-WSC peer method, but will probably end up being moved into higher layer for better configuration. EAP-WSC peer method for
* Added preliminary Wi-Fi Protected Setup (WPS) implementationJouni Malinen2008-11-231-0/+29
This adds WPS support for both hostapd and wpa_supplicant. Both programs can be configured to act as WPS Enrollee and Registrar. Both PBC and PIN methods are supported. Currently, hostapd has more complete configuration option for WPS parameters and wpa_supplicant configuration style will likely change in the future. External Registrars are not yet supported in hostapd or wpa_supplicant. While wpa_supplicant has initial support for acting as an Registrar to configure an AP, this is still using number of hardcoded parameters which will need to be made configurable for proper operation.