path: root/wpa_supplicant/README-WPS
diff options
authorJouni Malinen <jouni@qca.qualcomm.com>2013-02-15 09:45:29 (GMT)
committerJouni Malinen <j@w1.fi>2013-02-15 09:47:52 (GMT)
commitbbf41865c90c2e16510712fa32290729c194422d (patch)
tree499cebbd8000a7ac666d27382ee3bf0be45a23e4 /wpa_supplicant/README-WPS
parent23ffcaf172f2b601abd423ff2e9cd9d78773ce92 (diff)
WPS: Add support for config token generation with wpa_supplicant
When wpa_supplicant is controlling an AP mode interface, it can generate the NFC configuration token similarly to the way this is done in hostapd. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
Diffstat (limited to 'wpa_supplicant/README-WPS')
1 files changed, 10 insertions, 0 deletions
diff --git a/wpa_supplicant/README-WPS b/wpa_supplicant/README-WPS
index 1ea9843..a024ac8 100644
--- a/wpa_supplicant/README-WPS
+++ b/wpa_supplicant/README-WPS
@@ -336,6 +336,16 @@ wps_nfc_dh_privkey, wps_nfc_dev_pw) or generated dynamically with
tokens during manufacturing (each station needs to have its own random
+The "wps_nfc_config_token <WPS/NDEF>" command can be used to build an
+NFC configuration token when wpa_supplicant is controlling an AP
+interface (AP or P2P GO). The output value from this command is a
+hexdump of the current AP configuration (WPS parameter requests this to
+include only the WPS attributes; NDEF parameter requests additional NDEF
+encapsulation to be included). This data needs to be written to an NFC
+tag with an external program. Once written, the NFC configuration token
+can be used to touch an NFC interface on a station to provision the
+credentials needed to access the network.
If the station includes NFC interface and reads an NFC tag with a MIME
media type "application/vnd.wfa.wsc", the NDEF message payload (with or
without NDEF encapsulation) can be delivered to wpa_supplicant using the