Cryptographic Key Validation Against Weak Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Lattice-based cryptography systems face issues with weak keys, which can compromise confidentiality and reveal private key information due to the use of weak public keys, particularly in noisy multiplication-based schemes.
Innovation Solution
Implementing a validation procedure to assess the security of public keys before encapsulation or decapsulation, involving statistical measures such as magnitude checks, histogram analysis, and distance metrics to ensure the key is within expected ranges, thereby preventing the use of weak keys that could leak sensitive information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If lattice-based cryptography systems use noisy multiplication-based schemes for key exchange, then key exchange functionality is achieved, but weak public keys can compromise confidentiality and reveal private key information
Solution Approach 1:
The validation procedure performs preliminary checks on public keys before they are used in cryptographic operations. The system evaluates statistical measures such as magnitude checks, histogram analysis, and distance metrics to detect weak keys in advance, preventing their use in encapsulation or decapsulation operations that could compromise security
Solution Approach 2:
The validation procedure acts as an intermediary layer between key exchange and cryptographic operations. It introduces additional verification steps that assess whether public keys meet security criteria before allowing them to proceed to encapsulation/decapsulation, thereby blocking weak keys without affecting legitimate key exchange
2Reliability
If public keys are validated using statistical measures and validation procedures, then security against weak keys is improved, but computational overhead and processing time increase
Solution Approach 1:
The validation procedure implements a tiered approach where multiple statistical measures are applied, but not all measures are executed with equal depth for every key. The system performs essential checks (such as magnitude validation) that provide sufficient security improvement while avoiding excessive computational overhead from applying all possible validation techniques at maximum intensity
Data Source
AI summary
Some embodiments are directed to a second cryptographic device (20) and a first cryptographic device (10). The first and second cryptographic devices may be configured to transfer a key seed. The key seed may be protected using a public key from one party and a private key from the other party. For example, a public key may be obtained from a private key through a noisy multiplication. At least one of the first and second cryptographic device may validate an obtained public key, e.g., to avoid leakage of the key seed or of a private key.