Browser-Based End-to-End Encryption for Ad Hoc Sessions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing encryption methods that rely heavily on servers, such as Proton Mail, pose security risks due to potential vulnerabilities and the need for secure information exchange.
Innovation Solution
Implementing end-to-end encrypted ad hoc communication using a web browser, where encryption keys are stored locally and sessions are managed within RAM or local storage, ensuring secure communication without server involvement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If encryption relies heavily on servers, then centralized management and ease of operation are improved, but security and privacy are worsened due to potential server breaches
Solution Approach 1:
The patent extracts the encryption keys from the server environment and stores them locally in the user's web browser. The private key is generated and stored in the user's device memory, while only the public key is transmitted to the server for matching purposes. This extraction eliminates the security vulnerability of storing sensitive encryption materials on centralized servers.
Solution Approach 2:
The encryption system is segmented into client-side key generation and storage, and server-side key matching only. The server's role is limited to storing public keys and facilitating connections, while all sensitive cryptographic operations occur locally in the user's browser. This segmentation isolates the security-critical functions from the server infrastructure.
2Reliability
If encryption keys are stored locally in browser, then security is improved by reducing server breach risks, but device complexity increases
Solution Approach 1:
The user's web browser autonomously generates encryption key pairs, stores them securely in local memory, and manages the cryptographic operations without requiring user intervention. The browser automatically handles key persistence across sessions and coordinate exchange with the server, making the complex key management transparent to the user.
Solution Approach 2:
The server acts as an intermediary that facilitates key matching between users without handling sensitive private keys. It stores public keys and enables the matching process, while all security-critical operations remain client-side. This intermediary approach simplifies client-side complexity by offloading the coordination burden to the server.
3Reliability
If ad hoc communication is implemented without server involvement, then privacy is improved, but ease of operation worsens due to manual key exchange
Solution Approach 1:
Encryption key pairs are generated and stored in the user's browser before any communication takes place. The private key is created locally and securely stored in the device's memory, while the public key is prepared for transmission. This preliminary key generation eliminates the need for complex real-time key exchange during communication sessions.
Solution Approach 2:
The server serves as a trusted intermediary that facilitates the exchange of public keys between users. Users can communicate through the server using their pre-generated key pairs, and the server enables matching without exposing private keys. This intermediary approach maintains privacy while simplifying the operational complexity of key exchange.
Data Source
AI summary
A method for end to end encrypted (ETEE) communication, the method is executed by a web application of a first user and may include (a) participating in creating first user ETEE communication metadata; wherein the first user ETEE metadata comprise a first user identifier and one or more first user keys; (b) receiving a request from the first user to initiate a ETEE communication session with a second user that has a second user ETEE communication metadata; (c) determining an existence of ETEE communication session metadata, the ETEE communication session metadata facilitates an establishment of a session between the first user and the second user; (d) requesting to receive, from a ETEE communication service, the ETEE communication session metadata when not finding the ETEE communication session metadata; and (e) participating in establishing and maintaining the session between the first user and the second user when finding or receiving the ETEE communication session metadata.