Library File Signature Verification for Secure Callback Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data protection methods are vulnerable to unauthorized access when a secure file and security application are copied to another computer, as malicious attackers can provide counterfeit callback functions that falsely report stable system values, allowing access to data at unauthorized locations.
Innovation Solution
Signing a library file containing a callback function and securely storing the signature within the secure file, involving an initialization process to calculate and store signatures of trusted and untrusted library files, and only allowing access when a successful comparison of these signatures indicates the integrity of the library file.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a security application allows an application to provide its own callback function to access stable system values, then application-specific security is enhanced, but the system becomes vulnerable to counterfeit callback functions that can falsely report stable system values
Solution Approach 1:
The patent applies preliminary action by calculating and storing a signature of the trusted library file during an initialization process before the actual access control operation. This pre-computed signature is then used for verification during the use process, allowing the system to prevent counterfeit callback functions before they can compromise security.
Solution Approach 2:
The patent introduces a signature as an intermediary element that mediates between the trusted library file and the access control function. The signature serves as a verification mechanism that allows the system to trust the callback function without directly trusting the source, thus resolving the contradiction between adaptability and reliability.
2Adaptability or versatility
If the secure file and security application are copied to another computer, then data portability is improved, but malicious attackers can provide counterfeit callback functions to gain access at unauthorized locations
Solution Approach 1:
The system performs preliminary action by pre-calculating and storing the signature of the trusted library file during initialization. This allows the system to maintain security verification capabilities even when copied to another computer, preventing counterfeit callback functions from gaining unauthorized access while preserving data portability.
Solution Approach 2:
The signature acts as an intermediary that travels with the secure file when copied to another computer. This intermediary element enables the system to verify the integrity of the callback function at the new location, thus maintaining security while enabling data portability.
3Reliability
If signature verification of library files is implemented, then security against counterfeit callback functions is improved, but the access control process becomes more complex
Solution Approach 1:
The patent reduces complexity by performing the computationally intensive signature calculation during initialization and storing it for later use. During the actual access control operation, only a simple comparison between the stored signature and the calculated signature of the loaded library file is needed, thus maintaining high security while minimizing process complexity.
Solution Approach 2:
The patent segments the security verification process into two distinct phases: initialization (where the signature is calculated and stored) and use (where the signature is verified by comparison). This segmentation allows the complex computation to be performed once during setup, while the operational phase remains simple and efficient.
Data Source
AI summary
Techniques are provided for providing access to a stored secret using a callback function that generates stable system values. The callback function, which is stored in a library file, is verified by securely storing a signature of the library file and later generating another signature of the library file. Access to the stored secret using the callback function is only permitted when the callback function is verified.