Server-Based WPS PIN Authentication for Secure Wi-Fi Setup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Wi-Fi Protected Setup (WPS) protocol requires users to manually input a PIN for secure wireless connections, which is cumbersome and vulnerable to brute-force attacks, especially when static PINs are used across multiple devices.
Innovation Solution
A server-based WPS-PIN procedure that generates a one-time PIN on the enrollee device, encrypts it using a public key of a cloud server, and sends it to a connected device, which then decrypts and returns the PIN for secure authentication and credential provisioning without user intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual PIN input is used for WPS authentication, then security is provided, but user convenience deteriorates and brute-force attacks become feasible
Solution Approach 1:
The system performs automatic authentication without user intervention. The enrollee device generates a PIN, the connected device retrieves it via API, and authentication proceeds automatically, eliminating manual PIN input while maintaining security through the WPS protocol
Solution Approach 2:
An API server acts as an intermediary between the connected device and the enrollee device. The API server stores and manages PINs, allowing the connected device to retrieve PINs programmatically without direct user input, thus automating the authentication process while preserving security
2Ease of operation
If static PINs are used across multiple devices, then ease of operation improves, but security deteriorates due to brute-force vulnerability
Solution Approach 1:
The system transitions from static PINs to dynamic, device-specific PINs. Each enrollee device receives a unique PIN generated specifically for that device, making brute-force attacks ineffective while maintaining automated connection simplicity through the API retrieval process
Solution Approach 2:
Each device receives a customized PIN tailored to its specific identity and context. The PIN is generated locally for each enrollee device rather than using a universal static PIN, providing localized security while maintaining operational simplicity through automated retrieval
3Reliability
If one-time PINs are generated per device, then security against brute-force attacks improves, but device complexity increases
Solution Approach 1:
The PIN management complexity is extracted from the individual devices and centralized on the API server. The server handles PIN generation, storage, and distribution, allowing devices to simply retrieve their PINs via API calls without implementing complex PIN management logic locally
Solution Approach 2:
The API server serves as an intermediary that manages the complexity of generating and distributing unique PINs. Devices interact with the server through simple API calls rather than implementing their own PIN generation and management systems, reducing device complexity while maintaining security
Data Source
AI summary
Techniques for providing a server-based Wi-Fi Protected Setup (WPS) PIN procedure are described. In an example, a computing device generates a PIN associated with a WPS-PIN procedure. The computing device encrypts the PIN to generate an encrypted PIN based on a public key associated with a server. Further, the computing device sends, to another computing device that is communicatively coupled with the server via an access point, a WPS probe request that includes the encrypted PIN. Based on the WPS probe request, the computing device receives, from at least one of the other computing devices or the server, a credential associated with the access point. The computing devices connects to the access point based on the credential.