Cryptographic Key Pair Integrity Verification via Repeated Testing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current integrity tests for cryptographic key pairs may not detect errors effectively, particularly during key generation, which can lead to vulnerabilities in cryptographic systems and potential attacks.

Innovation Solution

A method involving repeated execution of integrity tests using different messages, with each iteration generating and comparing results to enhance the reliability of key pair verification, and an additional step to perturb the computation of the least common multiple to test electronic devices' resistance to errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If current integrity tests (single execution) are used for key pair verification, then the computational cost is low, but the reliability of detection is insufficient

Engineering Contradiction:
Improvedetection reliabilityVSAvoidcomputational cost
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies periodic action by executing the integrity test multiple times (at least twice) with different test data. Each execution uses a different message to encrypt/decrypt or sign/verify, and all results must be consistent for the key pair to be considered valid. This repeated periodic testing significantly improves detection reliability while keeping each individual test computationally efficient.

Inventive Principle:
Principle #19Periodic action

2Measurement precision

If multiple integrity tests are executed with different messages, then the probability of detecting corrupted key pairs increases, but the computational time increases

Engineering Contradiction:
Improveerror detection accuracyVSAvoidverification time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent implements partial or excessive action by performing a minimum of two integrity test executions, which provides sufficient error detection capability without excessive computational overhead. This number balances the need for high detection accuracy with acceptable verification time, ensuring that corrupted key pairs are detected with high probability while maintaining efficient operation.

Inventive Principle:
Principle #16Partial or excessive action

3Object-affected harmful factors

If integrity testing is performed during key generation, then vulnerabilities can be identified early, but the key generation process becomes more complex

Engineering Contradiction:
Improvevulnerability detectionVSAvoidkey generation process complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by performing integrity tests during the key generation process itself, before the keys are deployed for actual cryptographic operations. This allows vulnerabilities to be detected and corrected early in the key lifecycle, preventing compromised keys from being used in production systems. The complexity added is minimal since the same cryptographic operations are performed with additional verification steps.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9680645B2Integrity verification of cryptographic key pairs
Publication Date: 2017.06.13 IDEMIA FRANCE SAS
  • US9680645B2 patent drawing
  • US9680645B2 patent drawing
  • US9680645B2 patent drawing

AI summary

Method of integrity verification of cryptographic key pairs, the method including an integrity test with:at least one first step implementing one of the private and public keys and an initial test datum, the first step making it possible to generate a first result,at least one second step implementing at least the first result and the key not used during the at least one first step, the second step making it possible to generate a second result, anda comparison of the second result and of the initial test datum, characterized in that the test is re-executed upon each positive comparison, and in that the test is executed at least 2 times.