Private Key Update Without Public Key Change
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for updating private keys in asymmetric key-based systems require changing the public key when the private key is suspected to be leaked, leading to increased computational and management burdens, especially when switching between platform providers, and do not effectively prevent unauthorized access by old providers.
Innovation Solution
A method and system for efficiently updating a private key of a host entity by negotiating new parameters with a key issuer, allowing the private key to be changed without altering the corresponding public key, and revoking the old private key to prevent unauthorized access, using a group public key generated by the key issuer.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the public key is changed when updating the private key, then security is improved by preventing unauthorized access, but device complexity and management burden increase due to replacing identity in all services
Solution Approach 1:
The patent separates the public key (identity) from the private key (credential). The public key remains constant as a stable identity identifier, while the private key can be updated independently. This segmentation allows security updates without changing the identity, resolving the contradiction between security improvement and management complexity.
Solution Approach 2:
The patent introduces a key issuer as an intermediary that manages the relationship between public keys and private keys. The key issuer enables private key updates while maintaining the same public key identity, acting as a mediator that resolves the conflict between security requirements and operational simplicity.
2Reliability
If computational resources are increased for key pair regeneration, then security credentials can be updated, but productivity decreases due to extra computational burden
Solution Approach 1:
The patent establishes key parameters and relationships in advance during key generation, creating a framework where private keys can be updated without regenerating the entire key pair. This preliminary setup reduces computational burden during updates, resolving the contradiction between security credential updates and computational efficiency.
3Adaptability or versatility
If the private key is kept constant across platform providers, then identity consistency is maintained, but security is compromised as old providers can still access credentials
Solution Approach 1:
The patent makes the private key dynamic while keeping the public key static. The private key can be updated independently based on security requirements, allowing the system to adapt to different platform providers while maintaining identity consistency through the unchanged public key. This resolves the contradiction between identity consistency and credential security.
Data Source
Figure 1~11
Figure 2
Figure 3
AI summary
There is provided mechanisms for updating a private key of a host entity. The private key is based on parameters negotiated between the host entity and a key issuer. The host entity further has a group public key that is generated by the key issuer and associated with the private key. A method is performed by the host entity. The method comprises obtaining a need to acquire a new private key. The method comprises, in response thereto, performing a private key update procedure with the key issuer using the public key and the current private key, wherein parameters for the new private key are negotiated with the key issuer. The method comprises generating the new private key using the negotiated parameters.