Asymmetric Key Messaging Server Security Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing secure messaging solutions face security risks due to the use of symmetric key encryption, where a compromised messaging server or handset can expose all connected handsets to key compromise, leading to complex rekeying processes.
Innovation Solution
A method for transmitting encrypted messages from a messaging server to a handset using asymmetric key encryption, where the handset generates and stores a public key, and the messaging server uses this key to encrypt messages, ensuring that only the private key on the handset can decrypt them, thus isolating the risk to individual handsets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If symmetric key encryption is used for secure messaging, then message encryption and decryption can be performed efficiently, but the security risk increases because a compromised messaging server or handset exposes all connected handsets to key compromise
Solution Approach 1:
The patent segments the encryption system by assigning unique asymmetric key pairs to each handset. Instead of using a single symmetric key for all handsets, each handset generates its own public-private key pair, and the messaging server stores only the public keys. This segmentation isolates security risks to individual handsets, so that compromise of one handset does not affect others.
Solution Approach 2:
The patent transitions from symmetric key encryption to asymmetric key encryption. Each handset has a unique public key (shared with the server) and a private key (kept secret on the handset). The server encrypts messages using the recipient's public key, and only the recipient can decrypt with their private key. This asymmetry eliminates the need for the server to hold secret keys, thereby reducing security risks while maintaining encryption efficiency.
2Reliability
If a messaging server stores encryption keys for multiple handsets, then message delivery can be secured, but the complexity of rekeying increases significantly when keys are compromised
Solution Approach 1:
The patent extracts the secret key material from the messaging server and places it exclusively on the handsets. The server stores only public keys, which are mathematically one-way functions and cannot be used to derive the private keys. This extraction eliminates the security vulnerability of centralized key storage while maintaining secure message delivery, and simplifies rekeying since each handset independently manages its own key pair.
Solution Approach 2:
The patent introduces public keys as an intermediary between the server and the private keys on handsets. The server uses public keys to encrypt messages without ever needing to access or store the corresponding private keys. This intermediary mechanism allows secure message delivery while isolating the server from sensitive key material, thereby reducing both security risks and rekeying complexity.
3Reliability
If asymmetric key encryption is implemented with unique key pairs for each handset, then security risk is isolated to individual handsets, but the key management process becomes more complex
Solution Approach 1:
The patent implements self-service key management where each handset autonomously generates its own asymmetric key pair. The handset creates the public and private keys locally, stores the private key securely, and provides only the public key to the messaging server. This self-service approach eliminates the need for centralized key distribution and management infrastructure, reducing key management complexity while maintaining security isolation.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for transmitting an encrypted message from a messaging server (106) to a handset (104) comprising the steps of receiving, at the messaging server (106) and from a sender computer (102), a message to be sent to the handset (104) and a handset identifier associated with the handset and determining that the handset is not registered with the messaging server (106) by determining that the handset identifier does not have an associated handset encryption key stored at the messaging server. The handset (104) is registered by sending a notification to the handset requesting registration, receiving back a handset encryption key associated with the handset identifier; and storing the handset encryption key against the handset identifier at the messaging server which is to be used to encrypt the received message before sending. Prior to registering the handset (104), intermediate encryption of the message may be employed to create an intermediate encrypted message to be stored at the messaging server.