Encrypted Messaging Device Verification Without Private Key Sharing

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing messaging systems face challenges in securely authorizing secondary devices to send and receive encrypted messages without sharing private encryption keys, particularly when the primary device is unavailable or inconvenient for use.

Innovation Solution

A system where a primary device verifies a secondary device using physical interaction (e.g., scanning a QR code) to generate cryptographic credentials, which are then used to establish an encrypted communication session without relying on a central server for verification, ensuring the secondary device is authorized by maintaining a list of approved devices and using secret pairing keys.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a primary device is used to verify and authorize secondary devices in an encrypted messaging system, then communication security is improved, but device complexity and user operation difficulty increase

Engineering Contradiction:

Improvecommunication securityVSAvoiddevice authorization complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses QR codes as visual copies of cryptographic credentials that can be scanned and verified without exposing the actual encryption keys. The QR code contains encoded device identity information that can be read optically, creating a safe copy mechanism for device verification

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent introduces a server as an intermediary that facilitates device verification by receiving cryptographic proofs from secondary devices and coordinating with primary devices. This intermediary handles the complex verification logic, reducing the burden on end-user devices

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If encryption credentials are shared between primary and secondary devices, then device authorization is simplified, but security risk increases due to potential key exposure

Engineering Contradiction:

Improvedevice authorization easeVSAvoidsecurity risk

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent segments cryptographic credentials into distinct components: device identity keys stored securely in hardware, QR codes containing only public verification information, and cryptographic proofs generated temporarily during verification. This segmentation ensures that sensitive private keys never leave the secure hardware environment

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent uses temporary cryptographic proofs and one-time QR codes for device verification. These credentials are generated, used immediately for verification, and then discarded, preventing long-term exposure risks. The verification process uses ephemeral keys that are never stored persistently

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

3Productivity

If a central server manages device verification, then system coordination is improved, but reliance on the server increases potential attack vectors

Engineering Contradiction:

Improvesystem coordination efficiencyVSAvoidattack surface

Core Design Contradiction:

ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent enables primary devices to perform verification autonomously by scanning QR codes and validating cryptographic proofs locally using stored trust anchors. The primary device self- verifies the secondary device's credentials without requiring real-time server intervention, reducing the attack surface while maintaining coordination through periodic server updates

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS12500934B2Methods, mediums, and systems for verifying devices in an encrypted messaging system

Publication Date: 2025.12.16 WHATSAPP LLC

AI summary

This application describes methods, mediums, and systems for verifying a device for use in a messaging system. Using the device verification procedures described, a messaging system can securely authorize new devices to send and receive encrypted messages on behalf of a user, preferably without the need to share a private encryption key between the users' different devices. The application describes several techniques that can be used to provide such a system, including distributing a computer-perceptible code that encodes encryption information between a secondary device and a primary device. This allows the information to be distributed without intervention by a server. Other techniques provide unique ways to build and reverify authorized device lists, distribute encryption keys in chat channels, ensure that lists of authorized devices are distributed in the correct order and remain valid for an appropriate amount of time, add new devices to an ongoing or new conversation, and more.