path: root/wpa_supplicant/README-WPS
diff options
authorJouni Malinen <jouni.malinen@atheros.com>2010-09-23 17:30:52 (GMT)
committerJouni Malinen <j@w1.fi>2010-09-23 17:30:52 (GMT)
commit3981cb3cb81641813b1f51292032f2225ccdd70b (patch)
treebf6e7f50a8fcddc8b7e16ccc1fe4923464f51b68 /wpa_supplicant/README-WPS
parentfa37511fa7e9d6a8f4fdaa8ec2df4af71bac7941 (diff)
WPS: Add wps_check_pin command for processing PIN from user input
UIs can use this command to process a PIN entered by a user and to validate the checksum digit (if present).
Diffstat (limited to 'wpa_supplicant/README-WPS')
1 files changed, 7 insertions, 0 deletions
diff --git a/wpa_supplicant/README-WPS b/wpa_supplicant/README-WPS
index 7c28836..8a773e2 100644
--- a/wpa_supplicant/README-WPS
+++ b/wpa_supplicant/README-WPS
@@ -94,6 +94,13 @@ pushbutton event (for PBC) to allow a new WPS Enrollee to join the
network. wpa_supplicant uses the control interface as an input channel
for these events.
+The PIN value used in the commands must be processed by an UI to
+remove non-digit characters and potentially, to verify the checksum
+digit. "wpa_cli wps_check_pin <PIN>" can be used to do such processing.
+It returns FAIL if the PIN is invalid, or FAIL-CHECKSUM if the checksum
+digit is incorrect, or the processed PIN (non-digit characters removed)
+if the PIN is valid.
If the client device has a display, a random PIN has to be generated
for each WPS registration session. wpa_supplicant can do this with a
control interface request, e.g., by calling wpa_cli: