Digital Certificate Verification via Hashstamp Recording
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current digital certificate systems in code signing are vulnerable to theft and misuse, leading to security breaches and unauthorized modifications, with existing solutions failing to effectively prevent attacks on the trust chain and certificate verification processes.
Innovation Solution
A computer-implemented method and system that records digital certificate information on a second server, generates a hashstamp for signed software files, and verifies the integrity of the trust certificate chain, allowing users to check for any changes or anomalies, and automatically revoking compromised certificates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If digital certificates are used for code signing, then software authenticity and integrity are improved, but vulnerability to certificate theft and misuse increases
Solution Approach 1:
The system performs preliminary actions by recording the digital certificate and generating a hashstamp of the signed software file before distribution. This creates a pre-established reference point that enables later verification of whether the certificate and software have been compromised or altered.
Solution Approach 2:
The system implements feedback mechanisms by providing users with verification capabilities to check the current status of the recorded certificate and hashstamp. This allows continuous monitoring and detection of certificate misuse or software modification after the initial signing.
2Reliability
If certificate verification processes are implemented, then security against unauthorized modifications is improved, but complexity of the verification system increases
Solution Approach 1:
The system creates a copy of the digital certificate and generates a hashstamp (a simplified representation) of the signed software file. These copies serve as verification references that can be easily distributed and checked without requiring users to implement complex verification infrastructure.
Solution Approach 2:
The patent introduces a certificate recording system that acts as an intermediary, storing reference copies of certificates and software hashes. This intermediary simplifies the verification process for end users while maintaining security, as they only need to compare their received files against the recorded references rather than implementing full cryptographic verification chains.
3Ease of operation
If centralized certificate authority architecture is used, then certificate management is simplified, but availability and latency problems occur
Solution Approach 1:
The system segments the centralized certificate authority functionality by distributing recorded certificate copies and hashstamps to multiple locations or servers. This allows verification to occur locally or from multiple distributed points, eliminating the single point of failure and reducing latency for certificate verification.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer implemented method, a computer system and computer program product to prevent security problems in the use of digital certificates in code signing, The computer implemented method comprising a software distributor signing via a first server (300) at least one software file using a digital certificate with a digital signature and at least one user via a computing device (100) acquiring a copy of said signed software file, wherein said digital certificate to be used is previously recorded in a second server (200) in communication with said first server, the digital certificate to be recorded being provided by the software distributor upon a registration of the latter in said second server (200) and including information obtained from a trust certificate chain associated to the digital certificate when performing said registration, the second server (200) generating, upon a request made by the software distributor, a hashstamp of the signed software file.