Multiple Encoding Digital Signature Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current digital signature algorithms are inefficient in validating documents when converted from one encoding to another, as they require computationally expensive canonical conversion steps, rendering them ineffective for multiple encoding scenarios.
Innovation Solution
Creating a multiple encoding signature that includes hashes for various document encodings, allowing validation without the need for canonicalization by using labeled and encrypted hashes that can be efficiently matched to the document's encoding, even if converted.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If canonical encoding conversion is used to validate digital signatures, then signature validation reliability is improved, but computational cost and validation time increase significantly
Solution Approach 1:
The system pre-computes and stores hashes for multiple document encodings (PDF, XDP, XML) during the signature creation phase. When validation is needed, the system retrieves the pre-computed hash corresponding to the document's actual encoding, eliminating the need for time-consuming canonical conversion during validation. This preliminary computation of multiple encoding hashes resolves the contradiction by preparing validation data in advance.
Solution Approach 2:
The digital signature is divided into multiple independent hash components, each corresponding to a different document encoding. Instead of converting the entire document to a single canonical encoding, the system segments the signature validation into separate hash comparisons for each encoding type. This segmentation allows the system to validate signatures efficiently without requiring full document canonicalization.
2Reliability
If canonical encoding conversion is performed for signature validation, then signature integrity is ensured, but computational overhead increases
Solution Approach 1:
The system performs hash computation for multiple encodings during the signature creation phase rather than during validation. By pre-computing and storing these hashes, the system eliminates the need for energy-intensive canonical conversion operations during the validation phase, significantly reducing computational overhead while maintaining signature integrity.
Solution Approach 2:
Instead of converting the original document to a canonical encoding, the system creates and stores copies of hashes for multiple different encodings (PDF, XDP, XML) during signature creation. During validation, the system uses these pre-computed hash copies to verify signature integrity without requiring actual document conversion, thereby reducing computational overhead.
3Productivity
If digital signatures are created for specific encodings, then signature creation efficiency is improved, but adaptability to different encodings during validation is reduced
Solution Approach 1:
The digital signature system is designed to be universal by incorporating hashes for multiple document encodings (PDF, XDP, XML) within a single signature structure. This multi-functional signature can validate documents regardless of their specific encoding type, providing adaptability across different encoding formats while maintaining efficient creation processes through structured hash storage.
Solution Approach 2:
The system pre-computes and stores hashes for multiple encodings during the signature creation phase. This preliminary preparation of multi-encoding hash data enables the signature to adapt to various document encodings during validation without requiring re-computation or conversion, thus achieving both creation efficiency and validation adaptability.
Data Source
AI summary
Digitally signing data for multiple encodings is disclosed. A first signature of the data is generated. A second signature of a second encoding of the data is generated. The first signature and the second signature are associated with the signed data.