Wi-Fi Protected Setup

<h2 id="modes">Modes</h2>
The standard emphasizes <a href="/facts/Usability/zuAnqu9Q">usability</a> and <a href="/facts/Security/B4uxkyxh">security</a>, and allows four modes in a <a href="/facts/Home_network/1RmJ5nRn">home network</a> for adding a new device to the network:

PIN method
In which a PIN has to be read from either a sticker or display on the new <a href="/facts/Station_(networking)/qHEpFt1H">wireless device</a>. This PIN must then be entered at the "representant" of the network, usually the network's <a href="/facts/Wireless_access_point/701JjIzt">access point</a>. Alternately, a PIN provided by the access point may be entered into the new device. This method is the mandatory baseline mode and everything must support it. The <a href="/facts/Wi-Fi_Direct/TPsMzG4L">Wi-Fi Direct</a> specification supersedes this requirement by stating that all devices with a keypad or display must support the PIN method.<a class="footnote-ref" id="fnref:8" href="#fn:8">8</a>
Push button method
In which the user has to push a button, either an actual or virtual one, on both the access point and the new wireless client device. On most devices, this discovery mode turns itself off as soon as a connection is established or after a delay (typically 2 minutes or less), whichever comes first, thereby minimizing its vulnerability. Support of this mode is mandatory for access points and optional for connecting devices. The Wi-Fi Direct specification supersedes this requirement by stating that all devices must support the push button method.<a class="footnote-ref" id="fnref:9" href="#fn:9">9</a>
Near-field communication method
In which the user has to bring the new client close to the access point to allow a <a href="/facts/Near-field_communication/awqd3Ea8">near-field communication</a> between the devices. NFC Forum–compliant <a href="/facts/RFID/4CnmIV2b">RFID</a> tags can also be used. Support of this mode is optional.
USB method
In which the user uses a <a href="/facts/USB_flash_drive/Jv0qmTCF">USB flash drive</a> to transfer data between the new client device and the network's access point. Support of this mode is optional, but deprecated.
The last two modes are usually referred to as <a href="/facts/Out-of-band_data/K8UX1jR7">out-of-band</a> methods as there is a transfer of information by a channel other than the Wi-Fi channel itself. Only the first two modes are currently[when?] covered by the WPS certification. The USB method has been deprecated and is not part of the Alliance's certification testing.
Some wireless access points have a dual-function WPS button, and holding this button down for a shorter or longer time may have other functions, such as factory-reset or toggling WiFi.<a class="footnote-ref" id="fnref:10" href="#fn:10">10</a> [additional citation(s) needed]
Some manufacturers, such as <a href="/facts/Netgear/jCMtPgpD">Netgear</a>, use a different logo and/or name for Wi-Fi Protected Setup;<a class="footnote-ref" id="fnref:11" href="#fn:11">11</a> the Wi-Fi Alliance recommends the use of the Wi-Fi Protected Setup Identifier Mark on the hardware button for this function.<a class="footnote-ref" id="fnref:12" href="#fn:12">12</a>

<h2 id="technical-architecture">Technical architecture</h2>
The WPS protocol defines three types of devices in a network:

Registrar
A device with the authority to issue and revoke access to a network; it may be integrated into a <a href="/facts/Wireless_access_point/701JjIzt">wireless access point</a> (AP), or provided as a separate device.
Enrollee
A client device seeking to join a wireless network.<a class="footnote-ref" id="fnref:13" href="#fn:13">13</a>
AP
An access point functioning as a proxy between a registrar and an enrollee.
The WPS standard defines three basic scenarios that involve components listed above:

AP with integrated registrar capabilities configures an enrollee station (<a href="/facts/Station_(networking)/qHEpFt1H">STA</a>)
In this case, the session will run on the wireless medium as a series of <a href="/facts/Extensible_Authentication_Protocol/yuCAFHxC">EAP</a> request/response messages, ending with the AP disassociating from the STA and waiting for the STA to reconnect with its new configuration (handed to it by the AP just before).
Registrar STA configures the AP as an enrollee
This case is subdivided in two aspects: first, the session could occur on either a wired or wireless medium, and second, the AP could already be configured by the time the registrar found it. In the case of a wired connection between the devices, the protocol runs over <a href="/facts/Universal_Plug_and_Play/nrUmlpGr">Universal Plug and Play</a> (UPnP), and both devices will have to support UPnP for that purpose. When running over UPnP, a shortened version of the protocol is run (only two messages) as no authentication is required other than that of the joined wired medium. In the case of a wireless medium, the session of the protocol is very similar to the internal registrar scenario, but with opposite roles. As to the configuration state of the AP, the registrar is expected to ask the user whether to reconfigure the AP or keep its current settings, and can decide to reconfigure it even if the AP describes itself as configured. Multiple registrars should have the ability to connect to the AP. UPnP is intended to apply only to a wired medium, while actually it applies to any interface to which an IP connection can be set up. Thus, having manually set up a wireless connection, the UPnP can be used over it in the same manner as with the wired connection.
Registrar STA configures enrollee STA
In this case the AP stands in the middle and acts as an authenticator, meaning it only proxies the relevant messages from side to side.
<h2 id="protocol">Protocol</h2>

The WPS protocol consists of a series of <a href="/facts/Extensible_Authentication_Protocol/yuCAFHxC">EAP</a> message exchanges that are triggered by a user action, relying on an exchange of descriptive information that should precede that user's action. The descriptive information is transferred through a new Information Element (IE) that is added to the <a href="/facts/Beacon/anvMPAhs">beacon</a>, probe response, and optionally to the probe request and association request/response messages. Other than purely informative <a href="/facts/Type%25E2%2580%2593length%25E2%2580%2593value/IMeVVbpK">type–length–values</a>, those IEs will also hold the possible and the currently deployed configuration methods of the device.
After this communication of the device capabilities from both ends, the user initiates the actual protocol session. The session consists of eight messages that are followed, in the case of a successful session, by a message to indicate that the protocol is completed. The exact stream of messages may change when configuring different kinds of devices (AP or STA), or when using different physical media (wired or wireless).

<h2 id="band-or-radio-selection">Band or radio selection</h2>
Some devices with dual-band wireless network connectivity do not allow the user to select the 2.4 GHz or 5 GHz band (or even a particular radio or SSID) when using Wi-Fi Protected Setup, unless the wireless access point has separate WPS button for each band or radio; however, a number of later wireless routers with multiple frequency bands and/or radios allow the establishment of a WPS session for a specific band and/or radio for connection with clients which cannot have the SSID or band (e.g., 2.4/5 GHz) explicitly selected by the user on the client for connection with WPS (e.g. pushing the 5 GHz, where supported, WPS button on the wireless router will force a client device to connect via WPS on only the 5 GHz band after a WPS session has been established by the client device which cannot explicitly allow the selection of wireless network and/or band for the WPS connection method).<a class="footnote-ref" id="fnref:14" href="#fn:14">14</a><a class="footnote-ref" id="fnref:15" href="#fn:15">15</a>

<h2 id="security">Security</h2>

<h3>Online brute-force attack</h3>
In December 2011, researcher Stefan Viehböck reported a design and implementation flaw that makes <a href="/facts/Brute-force_attack/TXl8pkfb">brute-force attacks</a> against PIN-based WPS feasible to be performed on WPS-enabled Wi-Fi networks. A successful attack on WPS allows unauthorized parties to gain access to the network, and the only effective workaround is to disable WPS.<a class="footnote-ref" id="fnref:16" href="#fn:16">16</a> The vulnerability centers around the acknowledgement messages sent between the registrar and enrollee when attempting to validate a PIN, which is an eight-digit number used to add new WPA enrollees to the network. Since the last digit is a <a href="/facts/Checksum/AqxQ0I8g">checksum</a> of the previous digits,<a class="footnote-ref" id="fnref:17" href="#fn:17">17</a> there are seven unknown digits in each PIN, yielding 107 = 10,000,000 possible combinations.
When an enrollee attempts to gain access using a PIN, the registrar reports the validity of the first and second halves of the PIN separately. Since the first half of the pin consists of four digits (10,000 possibilities) and the second half has only three active digits (1000 possibilities), at most 11,000 guesses are needed before the PIN is recovered. This is a reduction by three <a href="/facts/Orders_of_magnitude/cWzRP2dM">orders of magnitude</a> from the number of PINs that would be required to be tested. As a result, an attack can be completed in under four hours. The ease or difficulty of exploiting this flaw is implementation-dependent, as Wi-Fi router manufacturers could defend against such attacks by slowing or disabling the WPS feature after several failed PIN validation attempts.<a class="footnote-ref" id="fnref:18" href="#fn:18">18</a>
A young <a href="/facts/Software_developer/WGTS1Jv9">software developer</a> based out of a small town in eastern New Mexico created a tool that exploits this vulnerability to prove that the attack is feasible.<a class="footnote-ref" id="fnref:19" href="#fn:19">19</a><a class="footnote-ref" id="fnref:20" href="#fn:20">20</a> The tool was then purchased by Tactical Network Solutions in Maryland. They state that they have known about the vulnerability since early 2011 and had been using it.<a class="footnote-ref" id="fnref:21" href="#fn:21">21</a>
In some devices, disabling WPS in the user interface does not result in the feature actually being disabled, and the device remains vulnerable to this attack.<a class="footnote-ref" id="fnref:22" href="#fn:22">22</a> <a href="/facts/Firmware/62UVKIUK">Firmware</a> updates have been released for some of these devices allowing WPS to be disabled completely. Vendors could also patch the vulnerability by adding a lock-down period if the Wi-Fi access point detects a brute-force attack in progress, which disables the PIN method for long enough to make the attack impractical.<a class="footnote-ref" id="fnref:23" href="#fn:23">23</a>

<h3>Offline brute-force attack</h3>
In the summer of 2014, Dominique Bongard discovered what he called the Pixie Dust attack. This attack works only on the default WPS implementation of several wireless chip makers, including Ralink, MediaTek, Realtek and Broadcom. The attack focuses on a lack of randomization when generating the E-S1 and E-S2 "secret" <a href="/facts/Cryptographic_nonce/ENHRCGnw">nonces</a>. Knowing these two nonces, the PIN can be recovered within a couple of minutes. A tool called pixiewps has been developed<a class="footnote-ref" id="fnref:24" href="#fn:24">24</a> and a new version of Reaver has been developed to automate the process.<a class="footnote-ref" id="fnref:25" href="#fn:25">25</a>
Since both the client and access point (enrollee and registrar, respectively) need to prove they know the PIN to make sure the client is not connecting to a rogue access point, the attacker already has two hashes that contain each half of the PIN, and all they need is to brute-force the actual PIN. The access point sends two hashes, E-Hash1 and E-Hash2, to the client, proving that it also knows the PIN. E-Hash1 and E-Hash2 are hashes of (E-S1 | PSK1 | PKe | PKr) and (E-S2 | PSK2 | PKe | PKr), respectively. The hashing function is <a href="/facts/HMAC/Qy9WD4V9">HMAC-SHA-256</a> and uses the "authkey" that is the key used to hash the data.

<h3>Physical security issues</h3>
All WPS methods are vulnerable to usage by an unauthorized user if the wireless access point is not kept in a secure area.<a class="footnote-ref" id="fnref:26" href="#fn:26">26</a><a class="footnote-ref" id="fnref:27" href="#fn:27">27</a><a class="footnote-ref" id="fnref:28" href="#fn:28">28</a> Many wireless access points have security information (if it is factory-secured) and the WPS PIN printed on them; this PIN is also often found in the configuration menus of the wireless access point. If this PIN cannot be changed or disabled, the only remedy is to get a firmware update to enable the PIN to be changed, or to replace the wireless access point.
It is possible to extract a wireless passphrase with the following methods using no special tools:<a class="footnote-ref" id="fnref:29" href="#fn:29">29</a>

<ul><li>A wireless passphrase can be extracted using WPS under <a href="/facts/Windows_Vista/IASEUCTB">Windows Vista</a> and newer versions of Windows, under administrative privileges by connecting with this method then bringing up the properties for this wireless network and clicking on "show characters".</li>
<li>Within most <a href="/facts/Linux_desktop/9FvCKSTq">Linux desktop</a> and <a href="/facts/Unix/0pNL2seI">Unix</a> distributions (like <a href="/facts/Ubuntu/0WDd7hkb">Ubuntu</a>), all network connections and their details are visible to a regular user, including the password obtained through WPS. Furthermore, <a href="/facts/Superuser/0Brr6ol7">root</a> (aka admin) can always access all network details through terminal, i.e. even if there is no <a href="/facts/Window_manager/WFRnDBz7">window manager</a> active for regular users.</li>
<li>A simple exploit in the Intel PROset wireless client utility can reveal the wireless passphrase when WPS is used, after a simple move of the dialog box which asks if you want to reconfigure this access point.<a class="footnote-ref" id="fnref:30" href="#fn:30">30</a></li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="https://www.wi-fi.org/knowledge-center/articles/wi-fi-protected-setup%E2%84%A2-0">Wi-Fi Protected Setup Knowledge Center</a> <a href="https://web.archive.org/web/20130324093221/http://www.wi-fi.org/knowledge-center/articles/wi-fi-protected-setup%25E2%2584%25A2-0">Archived</a> 2013-03-24 at the <a href="/facts/Wayback_Machine/nmQ3a6JC">Wayback Machine</a> at the Wi-Fi Alliance</li>
<li><a href="http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20080424.pdf">UPnP device architecture</a></li>
<li><a href="http://www.kb.cert.org/vuls/id/723755">US-CERT VU#723755</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1">"WPS Full Form". GeeksforGeeks. 2020-06-15. Retrieved 2025-05-02. <a href="https://www.geeksforgeeks.org/wps-full-form/" target="_blank">https://www.geeksforgeeks.org/wps-full-form/</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></li>
<li id="fn:2">"Where is the WPS Pin located on my hp printer?". Optimum Tech Help. 2023-01-19. Retrieved 2023-07-12. <a href="https://www.optimumtechhelp.com/where-is-the-wps-pin-located-on-hp-printer/" target="_blank">https://www.optimumtechhelp.com/where-is-the-wps-pin-located-on-hp-printer/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></li>
<li id="fn:3">Higgins, Tim (13 March 2008). "How is WPS supposed to work?". SmallNetBuilder. Retrieved 2020-05-01. <a href="https://www.smallnetbuilder.com/wireless/wireless-features/30345-how-is-wps-supposed-to-work" target="_blank">https://www.smallnetbuilder.com/wireless/wireless-features/30345-how-is-wps-supposed-to-work</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></li>
<li id="fn:4">"Wi-Fi Protected Setup (WPS) Vulnerable to Brute-Force Attack | CISA". www.cisa.gov. 2013-01-23. Retrieved 2025-04-28. <a href="https://www.cisa.gov/news-events/alerts/2012/01/06/wi-fi-protected-setup-wps-vulnerable-brute-force-attack" target="_blank">https://www.cisa.gov/news-events/alerts/2012/01/06/wi-fi-protected-setup-wps-vulnerable-brute-force-attack</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></li>
<li id="fn:5">Viehböck, Stefan (2011-12-26). "Brute forcing Wi-Fi Protected Setup" (PDF). Archived (PDF) from the original on 2012-01-18. Retrieved 2011-12-30. <a href="http://sviehb.files.wordpress.com/2011/12/viehboeck_wps.pdf" target="_blank">http://sviehb.files.wordpress.com/2011/12/viehboeck_wps.pdf</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></li>
<li id="fn:6">Allar, Jared (2011-12-27). "Vulnerability Note VU#723755 - WiFi Protected Setup PIN brute force vulnerability". Vulnerability Notes Database. US CERT. Archived from the original on 2017-12-07. Retrieved 2011-12-31. <a href="http://www.kb.cert.org/vuls/id/723755" target="_blank">http://www.kb.cert.org/vuls/id/723755</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></li>
<li id="fn:7">Gallagher, Sean (2012-01-04). "Hands-on: hacking WiFi Protected Setup with Reaver". Condé Nast Digital. Archived from the original on 2012-01-23. Retrieved 2012-01-20. <a href="https://arstechnica.com/business/news/2012/01/hands-on-hacking-wifi-protected-setup-with-reaver.ars" target="_blank">https://arstechnica.com/business/news/2012/01/hands-on-hacking-wifi-protected-setup-with-reaver.ars</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></li>
<li id="fn:8">P2P Spec 1.2, clause 3.1.4.3 <a href="#fnref:8" class="footnote-back-ref">↩</a></li>
<li id="fn:9">P2P Spec 1.2, <a href="#fnref:9" class="footnote-back-ref">↩</a></li>
<li id="fn:10">[1] Archived 2016-02-03 at the Wayback Machine Tenda W311R+ product page: long press causes factory reset. Retrieved 18 January 2016; Draytek: Vigor 2820 Series manual: short press toggles WiFi <a href="http://www.tendacn.com/en/product/W311R+.html" target="_blank">http://www.tendacn.com/en/product/W311R+.html</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></li>
<li id="fn:11">"Netgear N600 Wireless Dual Band Gigabit ADS2+ Modem Router DGND3700 User Manual" (PDF). www.netgear.com. Archived (PDF) from the original on April 4, 2015. Retrieved January 16, 2016. <a href="http://www.downloads.netgear.com/files/GDC/DGND3700/DGND3700_UM_11May11.pdf" target="_blank">http://www.downloads.netgear.com/files/GDC/DGND3700/DGND3700_UM_11May11.pdf</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></li>
<li id="fn:12">"Wi-Fi Alliance Brand Style Guide 2014" (PDF). www.wi-fi.org. Wi-Fi Alliance. April 2014. Archived from the original (PDF) on January 17, 2016. Retrieved January 16, 2016. <a href="https://web.archive.org/web/20160117000812/http://www.wi-fi.org/download.php?file=%2Fsites%2Fdefault%2Ffiles%2Fprivate%2FWi-Fi_Alliance_Brand_Styleguide-201404.pdf" target="_blank">https://web.archive.org/web/20160117000812/http://www.wi-fi.org/download.php?file=%2Fsites%2Fdefault%2Ffiles%2Fprivate%2FWi-Fi_Alliance_Brand_Styleguide-201404.pdf</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></li>
<li id="fn:13">"Wireless configuration using the PIN Method of Wi-Fi Protected Setup (For HL2170W)". www.uvm.edu. Retrieved 2025-05-02. <a href="https://www.uvm.edu/cosmolab/om/brother/html/nug/chapter7.html" target="_blank">https://www.uvm.edu/cosmolab/om/brother/html/nug/chapter7.html</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></li>
<li id="fn:14">[2] "D-Link DSL-2544N Dual Band Wireless N600 Gigabit ADSL2+ Modem Router User Manual, Version 1.0", Page 11, Retrieved 26 January 2016. <a href="http://files.dlink.com.au/products/DSL-2544N/Manuals/DSL-2544N_T1_Manual_v1.00%28AU%29.pdf" target="_blank">http://files.dlink.com.au/products/DSL-2544N/Manuals/DSL-2544N_T1_Manual_v1.00%28AU%29.pdf</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></li>
<li id="fn:15">NetComm NF8AC User Guide, Page 11, http://media.netcomm.com.au/public/assets/pdf_file/0004/142384/NF8AC-User-Guide.pdf Archived 2016-09-28 at the Wayback Machine, Retrieved October 16, 2016. <a href="http://media.netcomm.com.au/public/assets/pdf_file/0004/142384/NF8AC-User-Guide.pdf" target="_blank">http://media.netcomm.com.au/public/assets/pdf_file/0004/142384/NF8AC-User-Guide.pdf</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></li>
<li id="fn:16">Allar, Jared (2011-12-27). "Vulnerability Note VU#723755 - WiFi Protected Setup PIN brute force vulnerability". Vulnerability Notes Database. US CERT. Archived from the original on 2017-12-07. Retrieved 2011-12-31. <a href="http://www.kb.cert.org/vuls/id/723755" target="_blank">http://www.kb.cert.org/vuls/id/723755</a> <a href="#fnref:16" class="footnote-back-ref">↩</a></li>
<li id="fn:17">"Windows Connect Now–NET (WCN-NET) Specifications". Microsoft Corporation. 2006-12-08. Archived from the original on 2012-01-13. Retrieved 2011-12-30. <a href="http://download.microsoft.com/download/a/f/7/af7777e5-7dcd-4800-8a0a-b18336565f5b/WCN-Netspec.doc" target="_blank">http://download.microsoft.com/download/a/f/7/af7777e5-7dcd-4800-8a0a-b18336565f5b/WCN-Netspec.doc</a> <a href="#fnref:17" class="footnote-back-ref">↩</a></li>
<li id="fn:18">Viehböck, Stefan (2011-12-26). "Brute forcing Wi-Fi Protected Setup" (PDF). Archived (PDF) from the original on 2012-01-18. Retrieved 2011-12-30. <a href="http://sviehb.files.wordpress.com/2011/12/viehboeck_wps.pdf" target="_blank">http://sviehb.files.wordpress.com/2011/12/viehboeck_wps.pdf</a> <a href="#fnref:18" class="footnote-back-ref">↩</a></li>
<li id="fn:19">"reaver-wps". Archived from the original on 2012-01-02. Retrieved 2011-12-30. <a href="https://code.google.com/p/reaver-wps/" target="_blank">https://code.google.com/p/reaver-wps/</a> <a href="#fnref:19" class="footnote-back-ref">↩</a></li>
<li id="fn:20">"Reaver demonstration on WPS - proof of concept". Archived from the original on 2018-04-15. Retrieved 2015-02-14. <a href="http://www.kalitutorials.net/2014/04/hack-wpawpa2-wps-reaver-kali-linux.html" target="_blank">http://www.kalitutorials.net/2014/04/hack-wpawpa2-wps-reaver-kali-linux.html</a> <a href="#fnref:20" class="footnote-back-ref">↩</a></li>
<li id="fn:21">Dennis Fisher (2011-12-29). "Attack Tool Released for WPS PIN Vulnerability". Archived from the original on 2013-03-10. Retrieved 2011-12-31. This is a capability that we at TNS have been testing, perfecting and using for nearly a year. <a href="https://web.archive.org/web/20130310135915/https://threatpost.com/en_us/blogs/attack-tool-released-wps-pin-vulnerability-122911" target="_blank">https://web.archive.org/web/20130310135915/https://threatpost.com/en_us/blogs/attack-tool-released-wps-pin-vulnerability-122911</a> <a href="#fnref:21" class="footnote-back-ref">↩</a></li>
<li id="fn:22">Gallagher, Sean (2012-01-04). "Hands-on: hacking WiFi Protected Setup with Reaver". Condé Nast Digital. Archived from the original on 2012-01-23. Retrieved 2012-01-20. <a href="https://arstechnica.com/business/news/2012/01/hands-on-hacking-wifi-protected-setup-with-reaver.ars" target="_blank">https://arstechnica.com/business/news/2012/01/hands-on-hacking-wifi-protected-setup-with-reaver.ars</a> <a href="#fnref:22" class="footnote-back-ref">↩</a></li>
<li id="fn:23">Slavin, Brad (January 18, 2013). "Wi-Fi Security – The Rise and Fall of WPS". Netstumbler.com. Archived from the original on December 19, 2013. Retrieved December 17, 2013. <a href="http://www.netstumbler.com/2013/01/18/wi-fi-security-the-rise-and-fall-of-wps/" target="_blank">http://www.netstumbler.com/2013/01/18/wi-fi-security-the-rise-and-fall-of-wps/</a> <a href="#fnref:23" class="footnote-back-ref">↩</a></li>
<li id="fn:24">"pixiewps". GitHub. Archived from the original on 2015-08-04. Retrieved 2015-05-05. <a href="https://github.com/wiire/pixiewps" target="_blank">https://github.com/wiire/pixiewps</a> <a href="#fnref:24" class="footnote-back-ref">↩</a></li>
<li id="fn:25">"Modified Reaver". GitHub. Archived from the original on 2015-08-03. Retrieved 2015-05-05. <a href="https://github.com/t6x/reaver-wps-fork-t6x" target="_blank">https://github.com/t6x/reaver-wps-fork-t6x</a> <a href="#fnref:25" class="footnote-back-ref">↩</a></li>
<li id="fn:26">Scheck, Steven (2014-09-04). "WPS – Advantages and Vulnerability". ComputerHowtoGuide. Archived from the original on 2023-07-12. Retrieved 2023-07-12. <a href="https://www.computerhowtoguide.com/wps-advantages-vulnerability/" target="_blank">https://www.computerhowtoguide.com/wps-advantages-vulnerability/</a> <a href="#fnref:26" class="footnote-back-ref">↩</a></li>
<li id="fn:27">Hoffman, Chris (2017-07-10). "Wi-FI Protected Setup (WPS) is Insecure: Here's Why You Should Disable It". How-To Geek. Archived from the original on 2023-07-12. Retrieved 2023-07-12. <a href="https://www.howtogeek.com/176124/wi-fi-protected-setup-wps-is-insecure-heres-why-you-should-disable-it/" target="_blank">https://www.howtogeek.com/176124/wi-fi-protected-setup-wps-is-insecure-heres-why-you-should-disable-it/</a> <a href="#fnref:27" class="footnote-back-ref">↩</a></li>
<li id="fn:28">Tomáš Rosa, Wi-Fi Protected Setup: Friend or Foe Archived 2016-12-25 at the Wayback Machine, Smart Cards & Devices Forum, May 23, 2013, Prague, Retrieved October 16, 2016. <a href="http://crypto.hyperlink.cz/files/rosa_scadforum13.pdf" target="_blank">http://crypto.hyperlink.cz/files/rosa_scadforum13.pdf</a> <a href="#fnref:28" class="footnote-back-ref">↩</a></li>
<li id="fn:29">"An Emphasis On Physical Security For Wireless Networks", Bryce Cherry on Youtube, 8 April 2013, archived from the original on 2016-09-11, retrieved 2023-07-12 <a href="https://www.youtube.com/watch?v=kRhyvRAUG6k" target="_blank">https://www.youtube.com/watch?v=kRhyvRAUG6k</a> <a href="#fnref:29" class="footnote-back-ref">↩</a></li>
<li id="fn:30">"An Emphasis On Physical Security For Wireless Networks", Bryce Cherry on Youtube, 8 April 2013, archived from the original on 2016-09-11, retrieved 2023-07-12 <a href="https://www.youtube.com/watch?v=kRhyvRAUG6k" target="_blank">https://www.youtube.com/watch?v=kRhyvRAUG6k</a> <a href="#fnref:30" class="footnote-back-ref">↩</a></li>
</ol>

Wi-Fi Protected Setup open-in-new

Wi-Fi Protected Setup