Hardware-Specific Cryptographic Keys Using ECDH for Secure Software Decryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing encryption methods for software protection on hardware devices face challenges in securing encryption-decryption keys, particularly in environments with constrained resources, and often require complex infrastructure that is not feasible for all platforms.

Innovation Solution

Implementing Elliptic Curve Diffie-Hellman (ECDH) key exchange to generate hardware-specific cryptographic keys, where each device has a unique private key stored securely, allowing for dynamic key generation and decryption without exposing the private key to users, thus enhancing security and flexibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional encryption methods are used for software protection, then encryption-decryption keys can be established, but the keys become exposed to users and third parties, increasing the risk of compromise

Engineering Contradiction:
Improvekey securityVSAvoidkey exposure
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent extracts the private key from the software distribution process and stores it securely in hardware (e.g., TPM, secure element). The software only receives and uses the public key, eliminating the need to expose private keys to users or third parties while maintaining encryption functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces hardware-based key management systems (TPM, secure elements) as intermediaries between the software and the private key. These intermediaries securely store and manage the private keys, allowing software to be encrypted and distributed without compromising key security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If complex key management infrastructure is implemented, then key security is improved, but the infrastructure becomes too complex for platforms with constrained resources

Engineering Contradiction:
Improvekey securityVSAvoidinfrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses inexpensive, dedicated hardware security modules (TPM, secure elements) that can be integrated directly into the device. These relatively simple hardware components provide strong key protection without requiring complex software-based key management infrastructure.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Solution Approach 2:

The patent replaces complex software-based key management systems with simpler hardware-based solutions. By moving key storage and management to dedicated hardware components, the system achieves better security with reduced overall complexity compared to software-only approaches.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Ease of operation

If shared secrets are used between hardware manufacturers and software developers, then key exchange is enabled, but security is compromised when shared secrets are exposed

Engineering Contradiction:
Improvekey exchange capabilityVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts the secret key material from the shared secret model and places it in hardware-based secure storage on the device side. This eliminates the need for shared secrets between manufacturers and developers, as each device has its own unique private key stored securely in hardware.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent enables devices to generate and manage their own unique private keys in hardware security modules without requiring shared secrets from manufacturers or developers. Each device serves itself by generating its own key pair, eliminating the shared secret vulnerability while maintaining key exchange capability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS20250384147A1Hardware specific cryptographic key
Publication Date: 2025.12.18 ANALOG DEVICES INC
  • US20250384147A1 patent drawing
  • US20250384147A1 patent drawing
  • US20250384147A1 patent drawing

AI summary

System and techniques to generate a cryptographic key specific to a type of hardware are described herein. Software distribution and execution can use cryptographic keys tailored to specific hardware. A secret is generated from a hardware public key. The secret is used to create software public and private keys. The secret is used to protect the data and the public key is distributed with the software for use on a class of hardware to which the hardware private key is applicable. The hardware then uses the software public key and a local copy of the hardware private key to find the secret and decrypt the software to run the software locally.