Hashing With Private Key Components to Cut Signing Data Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing digital signature generation methods are inefficient and insecure due to the need to transport large data quantities over networks and expose cryptographic keys to potential attacks, especially when using new hash algorithms that require cryptographic device interaction.

Innovation Solution

A method involving appending or prepending a private key component (PKC) to the internal state of a hash function, allowing the hash to be generated client-side and minimizing network data transfer, while keeping the PKC within the cryptographic device's secure bounds.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the entire message is transmitted to the cryptographic device for signing, then the digital signature can be generated securely, but the network transmission time and data exposure to attacks increase significantly

Engineering Contradiction:
ImprovesecurityVSAvoidnetwork transmission time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The message is segmented into two parts: a hash of the message (generated client-side) and the signature request. Only the hash, not the entire message, is transmitted to the cryptographic device. This segmentation reduces network transmission time while maintaining security, as the hash uniquely represents the original message for verification purposes.

Inventive Principle:
Principle #1Segmentation

2Productivity

If the cryptographic key is exposed to generate the signature, then the signing process can be completed, but the key becomes vulnerable to attacks

Engineering Contradiction:
Improvesigning efficiencyVSAvoidkey exposure to attacks
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The private key is extracted from the signing process and kept securely within the cryptographic device. Only the public key and signature are exposed externally. This extraction eliminates key exposure vulnerabilities while maintaining signing efficiency, as the private key never leaves the secure cryptographic device boundaries.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If large data quantities are transmitted over the network for digital signing, then complete message verification is possible, but network bandwidth and transmission time are consumed

Engineering Contradiction:
Improvemessage verificationVSAvoiddata transmission volume
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The message data is transformed into a hash value, changing the parameter from large message size to small fixed-size hash. This parameter change enables complete message verification through the hash while dramatically reducing data transmission volume over the network.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250392476A1Hashing messages with cryptographic key components
Publication Date: 2025.12.25 GARANTIR LLC
  • US20250392476A1 patent drawing
  • US20250392476A1 patent drawing
  • US20250392476A1 patent drawing

AI summary

Techniques for hashing messages with cryptographic key components are provided. In one technique, a message to be hashed with a private key component is identified. During a hash operation relative to the message involving a hash function, the client identifies an internal state of the hash function, which internal state is based on the message. The client sends the internal state of the hash function to a cryptographic device. The cryptographic device identifies a private key component and generates a final hash based on the private key component and the internal state of the hash function. In another technique, a client receives, from a cryptographic device, an internal state of a hash function, where the internal state is based on a private key component that is stored in the cryptographic device. Based on the internal state and a message, the client generates a final hash.