Cryptographic Data Objects Page Conversion for Legacy I/O
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cryptographic Capability Computing (C3) faces compatibility issues with legacy software and device input/output operations due to the use of cryptographic pointers as tweak-keys for per-data object encryption, leading to problems with aliasing and memory allocation unknown to the allocator, which breaks the binding between pointers and their associated data objects.
Innovation Solution
The implementation of cryptographic data objects page conversion allows for the conversion of pages containing cryptographic data objects into plaintext, enabling legacy device input/output operations and aliasing, using a page table bit to indicate decryption and managing per-object cryptographic state and metadata to facilitate access through legacy input/output techniques.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If per-data object encryption using cryptographic pointers is implemented, then data security and confidentiality are improved, but compatibility with legacy software and device I/O operations deteriorates
Solution Approach 1:
The patent segments the memory management approach by introducing a page-level conversion mechanism that divides memory into cryptographic pages and legacy pages. This allows selective application of cryptographic protection at the page level rather than forcing all memory operations to use cryptographic pointers, thereby maintaining data security for protected pages while preserving compatibility for legacy operations on non-converted pages.
Solution Approach 2:
The patent introduces a page table entry bit as an intermediary mechanism that mediates between cryptographic requirements and legacy compatibility needs. This bit acts as a flag that indicates whether a page should be accessed through cryptographic pointers or through traditional plaintext pointers, allowing the system to bridge the gap between secure cryptographic access and legacy I/O operations without requiring changes to legacy software.
2Reliability
If cryptographic pointers are used as tweak-keys for per-object encryption, then data object security is improved, but aliasing and memory allocation compatibility deteriorate
Solution Approach 1:
The patent introduces dynamic page conversion capability that allows the system to convert pages between cryptographic and legacy modes based on operational requirements. This dynamic approach enables memory allocations to be flexible - they can be converted to cryptographic pages when security is needed and reverted to legacy pages when compatibility with device I/O or aliasing is required, without breaking the binding between pointers and data objects.
Solution Approach 2:
The patent changes the state parameter of memory pages by introducing a conversion mechanism that alters the cryptographic state of pages. By setting or clearing the page table entry bit, the system can change a page from an encrypted state to a plaintext state or vice versa, allowing memory allocations to adapt their cryptographic parameters based on whether they need to work with legacy device I/O operations or maintain cryptographic protection.
3Reliability
If binding between cryptographic pointer and encrypted data object is enforced, then cryptographic security is improved, but legacy device I/O operations deteriorate
Solution Approach 1:
The patent creates a universal memory access mechanism that can handle both cryptographic and legacy operations through the same page table infrastructure. The page table entry bit provides a unified control mechanism that directs access appropriately - cryptographic pointers for secure operations and plaintext pointers for legacy device I/O - allowing the system to support multiple operation types without requiring separate memory management systems for each.
Data Source
AI summary
A method comprises identifying a first page in a computer readable memory communicatively coupled to the apparatus that has been marked as being stored in memory as plaintext even if accessed using cryptographic addresses, the first page in the computer readable memory comprising at least one encrypted data object, and set a page table entry bit for the first page to a first value which indicates that at least one memory allocation in the first page has been marked as being stored in memory as plaintext even if accessed using cryptographic addresses.