Secure Wake on LAN White List Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Wake on LAN (WOL) technologies lack sufficient security, particularly in small networks, as they can be easily compromised by malicious devices intercepting passwords or wake-up packets, and existing solutions are not well-suited for home LANs.

Innovation Solution

Implementing a secure Wake on LAN system using a white list stored in the device's memory, which includes credentials for authorized entities, and a sleep manager logic that only wakes the device if the requesting entity's credentials are on the white list, ensuring only authorized entities can initiate the wake-up process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If Wake on LAN is enabled to allow remote device activation, then device accessibility is improved, but security vulnerability increases due to packet interception risks

Engineering Contradiction:
Improvedevice accessibilityVSAvoidsecurity vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary authentication by checking the requesting entity's credentials against the stored white list before activating the device. This advance verification prevents unauthorized wake-up requests from malicious devices while allowing legitimate remote activation, thus resolving the security vulnerability without compromising accessibility.

Inventive Principle:
Principle #10Preliminary action

2Object-affected harmful factors

If password protection is implemented for Wake on LAN, then security is improved, but ease of operation deteriorates due to password interception in packets

Engineering Contradiction:
ImprovesecurityVSAvoidoperation convenience
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The patent extracts the authentication credentials from the transmitted wake-up packets and stores them securely in the device's memory as a white list. By removing passwords from network packets and performing authentication locally using stored credentials, the system eliminates the security risk of packet interception while maintaining convenient operation for authorized users.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If existing Wake on LAN solutions are used in small networks, then device wake-up functionality is achieved, but security reliability deteriorates due to lack of suitable security measures

Engineering Contradiction:
Improvewake-up functionalityVSAvoidsecurity reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements localized security measures by storing authentication credentials specifically in the device's own memory rather than relying on network-level security. This local white list approach provides tailored security protection suitable for small networks, maintaining wake-up functionality while significantly improving security reliability through device-specific authentication.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9489023B1Secure wake on LAN with white list
Publication Date: 2016.11.08 MARVELL ASIA PTE LTD
  • US9489023B1 patent drawing
  • US9489023B1 patent drawing
  • US9489023B1 patent drawing

AI summary

Systems, methods, and other embodiments associated with secure Wake on LAN with white list are described. According to one embodiment, an apparatus includes memory and sleep manager logic. The memory is configured to store a white list. The white list includes credentials for entities that are authorized to wake a host device from a power-saving sleep mode. The sleep manager logic is configured to receive, from a requesting entity, a request to wake the host device and determine if credentials for the requesting entity are on the white list. The sleep manager logic is configured to wake the host device when credentials for the requesting entity are on the white list and refrain from waking the host device when credentials for the requesting entity are not on the white list.