Keystore Password Management via Volatile Memory Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing encryption methods are vulnerable to unauthorized access because passwords for keystores are often saved in file systems, making it possible for third parties to locate and obtain the passwords, even if they are hidden in obscure locations, allowing them to decrypt and encrypt messages.
Innovation Solution
The solution involves deleting the password from both the source and memory associated with the application after use, ensuring that the password is not accessible to unauthorized parties, thereby preventing access to the keystore and maintaining secure message transfer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the password is saved in a file system for keystore access, then the application can access the keystore and encrypt/decrypt messages, but the password becomes vulnerable to unauthorized access by third parties who can locate and obtain it from the file system
Solution Approach 1:
The patent extracts the password from persistent storage (file system) and keeps it only in volatile memory during runtime. The password is loaded into memory when the application starts and deleted when the application stops, eliminating the file system storage vulnerability while maintaining keystore accessibility during operation.
Solution Approach 2:
The patent treats the password as a short-living object that exists only temporarily in volatile memory during application execution. The password is automatically deleted from memory when the application stops, ensuring it does not persist in accessible locations. This disposable approach prevents unauthorized access while maintaining functionality during the brief period when the password is needed.
2Object-affected harmful factors
If the password is deleted from the file system source, then unauthorized access to the password is prevented, but the application cannot retrieve the password for keystore access
Solution Approach 1:
The patent performs preliminary action by loading the password from the file system into volatile memory before the application needs it for keystore access. The password is retrieved once at startup, stored securely in memory, and then the file system source can be deleted or left inaccessible. This preliminary loading ensures the application has the password available without requiring ongoing file system access.
Solution Approach 2:
The patent introduces volatile memory as an intermediary between the file system and the application. The password is transferred from the file system to volatile memory, where it resides during application execution. This intermediary approach allows the application to access the password without direct file system access, improving security while maintaining functionality.
3Productivity
If the password is retained in memory after use, then the application can quickly access it for subsequent operations, but the password remains accessible to unauthorized parties who can access the memory
Solution Approach 1:
The patent applies dynamics by making the password's presence in memory temporary and conditional. The password is loaded into memory when the application starts and automatically deleted when the application stops. This dynamic approach allows fast access during operation while eliminating the security risk of persistent memory storage. The password exists in memory only when absolutely necessary for keystore access.
Data Source
AI summary
Key retrieval can include accessing a password for a keystore from a source. Key retrieval can include placing the password in memory. Key retrieval can include deleting the password from the source. Key retrieval can include retrieving an encryption key from the keystore with the password in memory.