Browser-Based End-to-End Messaging With Verified Client-Side Cryptography

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing secure messaging and file-sharing technologies require users to install encryption programs on their devices and rely on untrusted servers for client-side scripting, posing risks of malicious code injection and compromising sensitive information.

Innovation Solution

Implement end-to-end encryption using client-side scripting in web browsers, ensuring messages are encrypted and decrypted within the browser without server access, and verify the integrity of downloaded files using cryptographic methods to prevent malicious code injection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If file sharing services use SSL/TLS connections and server-side encryption, then files are encrypted during transit and at rest, but the service provider can decrypt files at any time and files are unencrypted while in the service's possession

Engineering Contradiction:

Improveencryption securityVSAvoidserver access to unencrypted data

Core Design Contradiction:

ReliabilityVSObject-generated harmful factors

Solution Approach 1:

The encryption and decryption operations are extracted from the server environment and moved to the client's web browser. Client-side scripting implements the cryptographic operations locally, ensuring that the server never possesses the encryption keys or unencrypted data. The encrypted file is uploaded through SSL/TLS, remains encrypted on the server, and is decrypted only in the client's browser, eliminating the server's ability to access unencrypted content.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The web browser acts as an intermediary between the client and server, performing all cryptographic operations. The browser executes client-side scripting that handles encryption before upload and decryption after download, serving as a trusted intermediary that prevents the server from accessing sensitive unencrypted data while still enabling secure file sharing functionality.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If encryption programs are installed on sender and recipient devices, then true end-to-end encryption is achieved, but users must install special software and have technical know-how

Engineering Contradiction:

Improveend-to-end encryptionVSAvoidsoftware installation requirement

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The web browser, being a universal application already installed on most devices, is leveraged to perform encryption and decryption functions. Instead of requiring specialized encryption software, the invention uses the browser's existing infrastructure combined with client-side scripting to provide end-to-end encryption capabilities through a universally accessible platform, eliminating the need for additional software installation.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The traditional mechanical approach of installing dedicated encryption software is replaced with a web-based system using client-side scripting. The cryptographic operations that previously required standalone applications are now performed through scripts executed within the browser environment, substituting the need for separate software installations with integrated web-based functionality.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Ease of operation

If client-side scripting is used for encryption in web browsers, then no additional software installation is needed, but the server could inject malicious code compromising security

Engineering Contradiction:

Improveweb browser accessibilityVSAvoidsecurity against malicious code

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The client-side scripting code is downloaded and cached in the user's web browser before the actual file sharing operation occurs. This preliminary caching ensures that the encryption code is already present and trusted in the browser's local environment, preventing the server from injecting malicious code during the critical encryption and decryption operations. The code integrity is established beforehand, mitigating the risk of server-side code injection attacks.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12363080B2System and method for web-browser based end-to-end encrypted messaging and for securely implementing cryptography using client-side scripting in a web browser

Publication Date: 2025.07.15 MEIXLER TECH

AI summary

A system and method for sending end-to-end encrypted messages comprising a sender's web browser, a recipient's web browser, and a server. The system and method avoid both the sender and the recipient having to download encryption programs themselves onto their respective computers. In addition, the system and method ensure that unencrypted messages are never disclosed to the server. The system and method operate by first downloading the web browser files, verifying them and then preventing the web browser page from refreshing, thereby preventing malicious code from entering the web browser each time the web browser page would normally be refreshed. The system and method also provide for securely implementing cryptography using client-side scripting in a web browser.