Partner Token Asymmetric Encryption for Time-Limited Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional data encryption methods using a single cryptographic key are vulnerable to malicious actors, as sharing the key compromises security, and existing solutions do not adequately protect against unauthorized decryption.
Innovation Solution
Implementing two-password asymmetric encryption using time-constrained partner tokens, where each device generates a public key based on a unique password, forming an asymmetric key pair, and encrypts it within a token that expires after a limited time, ensuring secure data exchange without sharing private keys.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a single cryptographic key is shared between parties for encryption and decryption, then data exchange is enabled, but security is compromised as the key becomes vulnerable to malicious actors
Solution Approach 1:
The cryptographic key is segmented into two distinct components: a public key for encryption and a private key for decryption. This segmentation eliminates the need to share the decryption key while enabling data exchange, directly resolving the contradiction between operational ease and security.
Solution Approach 2:
The system employs asymmetric cryptography where the encryption key (public) and decryption key (private) are mathematically related but distinct. This asymmetry allows one party to encrypt data without needing access to the other party's decryption key, maintaining security while enabling communication.
2Reliability
If cryptographic keys are protected through additional security measures, then security is improved, but the complexity of the system increases
Solution Approach 1:
Each party independently generates their own key pair without requiring key distribution or coordination. The system is self-configuring, where each device autonomously establishes its cryptographic identity, reducing system complexity while maintaining strong security.
3Adaptability or versatility
If private key data is exchanged between parties, then mutual encryption capability is achieved, but the risk of compromise by malicious actors increases
Solution Approach 1:
The private key component is extracted from the exchange process entirely. Only public keys are transmitted between parties, while private keys remain securely stored locally on each device. This extraction eliminates the vulnerability to interception while preserving mutual encryption capability.
4Ease of operation
If partner tokens are made valid for extended periods, then usability is improved, but the window for potential unauthorized access increases
Solution Approach 1:
The partner token's validity period is made dynamic rather than static. The system automatically adjusts the token's lifespan based on security requirements, creating a balanced window that provides sufficient usability while limiting exposure to potential attacks. The token expires automatically after the designated period.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
Techniques for protecting data using two password asymmetric encryption based on time-constrained password-based partner tokens. To encrypt data, a first partner computing device receives a first partner token from a second computing device. The first partner computing device decrypts the first partner token to recover first public key data generated by the second partner computing device. The first partner computing device derives a cryptographic encryption key to encrypt the data based on the first public key data, and based on first private key data generated by the first partner computing device. The second computing device may decrypt the encrypted data based on a second partner token generated by the first partner computing device, using a cryptographic decryption key derived using second private key data generated by the second computing device and second public key data generated by the first computing device and embedded and encrypted in the second partner token.