Public Key Refresh Using Tamper-Resistant Ledger Commitment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing public-key cryptography systems are vulnerable to 'man-in-the-middle' attacks, where attackers intercept and alter public keys, compromising security during key refresh operations.
Innovation Solution
Implementing a tamper-resistant public key infrastructure using a ledger database that stores and manages multiple public keys, ensuring only valid and active keys are used, preventing the injection of unauthorized key pairs through tamper-evident ledger technology.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If public keys are refreshed to maintain security, then cryptographic security is improved, but the system becomes vulnerable to man-in-the-middle attacks during the refresh process
Solution Approach 1:
The system pre-generates multiple public keys and stores them in the ledger database before they are needed. When key refresh is required, the system can immediately switch to a pre-generated key without performing cryptographic operations during the transition, eliminating the vulnerability window for man-in-the-middle attacks.
Solution Approach 2:
The ledger database acts as a trusted intermediary that stores and manages public keys. The ledger manager coordinates key distribution and validation, ensuring that public keys are properly authenticated and distributed to computing devices, thereby preventing unauthorized key injection during the refresh process.
2Reliability
If multiple public keys are stored and managed in a ledger database, then key refresh security is improved, but system complexity increases
Solution Approach 1:
The ledger database serves multiple functions: storing public keys, validating key authenticity, managing key lifecycle, and providing a trusted source for key distribution. The ledger manager also performs multiple roles including key generation coordination, validation, and distribution. This multi-functionality reduces the need for separate dedicated components for each function.
Solution Approach 2:
The system includes automated key validation and refresh mechanisms that operate without manual intervention. The ledger manager automatically validates public keys against the ledger database, detects compromised keys, and triggers refresh operations when needed, reducing operational complexity despite the sophisticated security architecture.
Data Source
AI summary
Systems, methods, and computer readable storage media described herein provide key refreshment utilizing tamper-resistant public key commitment. In an aspect, a ledger manager stores a set of public keys associated with a user account in a ledger database. The ledger manager assigns a first public key of the set of public keys as an active key. Responsive to receiving an update key request from a computing device on behalf of the user account, the ledger manager updates the active key to a second public key of the set of public keys. Responsive to receiving an active key request from another computing device on behalf of a another user account, the ledger manager causes data accessible to the another computing device to be encrypted using the second public key. In an aspect, the ledger manager utilizes the second public key to encrypt second data accessible to the another computing device.