Client-Server Key Encryption Separation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional key encryption methods store the encryption algorithm locally on a client, making it vulnerable to attackers who can restore the key and decrypt encrypted data, compromising data security.
Innovation Solution
A key encryption system where the client only stores an information header encrypted by an algorithm, while the server stores the encryption algorithm, allowing the client to request and obtain the key using the stored header, ensuring the key is restored securely without storing the algorithm locally.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the encryption algorithm is stored locally in the client, then the key can be restored easily for data encryption, but the security of the key is compromised because attackers can obtain the algorithm and restore the key
Solution Approach 1:
The encryption algorithm is extracted from the client and stored on the server instead. The client only keeps the encrypted key, while the server holds both the encrypted key and the decryption algorithm. This separation ensures that even if the client is compromised, attackers cannot restore the key without the server's algorithm.
Solution Approach 2:
The server acts as an intermediary that holds the decryption algorithm. When key restoration is needed, the client sends the encrypted key to the server, which uses its stored algorithm to restore the key and return it to the client. This mediator approach prevents the client from having direct access to the algorithm.
2Reliability
If the encryption algorithm is not stored locally, then key security is improved, but the client cannot independently restore the key without server interaction
Solution Approach 1:
The system merges the key storage and algorithm storage into separate locations (client stores encrypted key, server stores algorithm), creating a distributed architecture that balances security and functionality without requiring the client to store sensitive algorithmic information.
3Reliability
If the encryption algorithm is not stored locally, then attackers cannot obtain it, but the client requires additional communication with the server to obtain the key
Solution Approach 1:
The encryption algorithm is pre-loaded and stored on the server in advance. When the client needs to restore a key, the server can immediately use the pre-stored algorithm without needing to retrieve or generate it at that moment, reducing the time delay for key acquisition.
Data Source
AI summary
Key encryption methods, apparatuses and systems are disclosed in the embodiments of the present disclosure. A client does not store an encryption algorithm used for encrypting a key, but only stores an information header encrypted by the encryption algorithm, so that an attacker cannot directly obtain the encryption algorithm that is used for decrypting the information header even if the client is attacked, thus improving the security of the key in the client. When the key is needed to be used to encrypt obtained data, the client can use the stored first information header to request the key from the server, and the server having a higher security restores the key based on a stored first encryption algorithm. The client can encrypt the data using the key obtained from the server, so that the client can ensure the security of the obtained data without storing the encryption algorithm.