Web Browser Cryptographic Key Decryption via Server Shares

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Asymmetric key cryptographic methods require private key installation and storage, making decryption and digital signature generation impractical on public or shared devices like computers, tablets, and smartphones, and necessitate users to remember or store lengthy private keys, compromising security and usability.

Innovation Solution

A method and system that provide executable code portions to web browsers to perform cryptographic processes, including requesting and decrypting an encrypted private key using an unlocking entity, allowing cryptographic requests to be fulfilled without local storage or key remembrance, compatible with any computing unit running a web browser.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If private key is stored locally or user remembers it, then cryptographic operations can be performed, but security is compromised and usability deteriorates due to lengthy key management

Engineering Contradiction:

Improvecryptographic operation capabilityVSAvoidkey management convenience

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent extracts the private key from local storage and user memory requirements by implementing it as a server-side secret. The private key is divided into shares using secret sharing, with one share stored on the server and another in the browser's secure storage, eliminating the need for users to manually manage lengthy private keys while maintaining cryptographic operation capability

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a server as an intermediary that holds a share of the private key. This server acts as a mediator between the user's browser and the cryptographic operations, enabling decryption and signature generation without requiring the user to directly manage the complete private key, thus improving both security and usability

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If private key is installed on computing unit, then cryptographic operations are enabled, but device compatibility is limited to devices with software installation capability

Engineering Contradiction:

Improvecryptographic operation capabilityVSAvoiddevice compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal cryptographic solution that works across multiple device types (smartphones, tablets, computers, shared devices) by using web browser-based cryptographic operations. The system uses standard web technologies and secure browser storage mechanisms that are universally available, eliminating the need for device-specific software installation while maintaining cryptographic functionality

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent replaces the traditional mechanical/software installation approach with a web-based system that uses browser JavaScript and secure storage APIs. This substitution eliminates the need for installing cryptographic software on each device, allowing cryptographic operations to be performed on any device with a modern web browser, thus significantly improving device compatibility

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Reliability

If private key is stored locally, then cryptographic operations can be performed, but security is compromised due to storage and transmission risks

Engineering Contradiction:

Improvecryptographic operation capabilityVSAvoidkey storage security risk

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the private key into multiple shares using secret sharing schemes. One share is stored securely on a server, while another share is stored in the browser's secure storage. Neither share alone can reconstruct the private key, eliminating the security risks associated with storing the complete private key locally while still enabling cryptographic operations when both shares are combined

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent converts the potential harm of key storage by implementing a system where the private key is never stored in its complete form. Instead, the system uses distributed key shares where the absence of complete key storage becomes a security feature rather than a limitation, transforming the storage problem into a security advantage

Inventive Principle:

Principle #22Blessing in disguise (Convert harm into benefit)

Data Source

PatentEP3229397B1Method for fulfilling a cryptographic request requiring a value of a private key

Publication Date: 2020.09.09 CONTACTOFFICE GRP

Figure 1~2
Figure 3
Figure 4

AI summary

Method for fulfilling a cryptographic request requiring a value of a private key. Code portions (100) are sent from a server (20) to a computing unit (60) running a web browser (10). The code portions (100) are executed directly in the web browser (10) in such a way that it automatically performs a cryptographic process 1 including the steps of: • receiving 11 a cryptographic request requiring a value of a private key; • requesting 12 an encrypted value of the private key; • receiving 13 the encrypted value of the private key; • requesting 14 an unlocking entity; • receiving 15 the unlocking entity; • decrypting 16 the encrypted value of the private key with the unlocking entity to obtain the value of the private key; and • fulfilling 17 the cryptographic request using the obtained value of the private key.