Digital Content Verification via Signed Device Public Key Tokens
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The evolution of digital content generation and dissemination has made it challenging to ensure the authenticity and integrity of digital content, such as images and videos, due to the accessibility of sophisticated editing tools, which undermines credibility across domains like digital media, journalism, and intellectual property rights.
Innovation Solution
A system and method involving a server and mobile device that utilize cryptographic techniques, including key signing and data token generation, to verify the origin and authenticity of digital content by generating and storing a signed device public key and data token, ensuring that content was generated on a specific app instance and has not been edited.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If cryptographic verification methods are implemented to ensure digital content authenticity, then content credibility and integrity are improved, but system complexity and computational overhead increase
Solution Approach 1:
The server signs the device public key in advance during content creation, creating a verified data token that contains the signed public key. This preliminary cryptographic verification eliminates the need for complex real-time verification during content sharing, as recipients can simply verify the pre-created token using the server's public key.
Solution Approach 2:
The verified data token is a self-contained copy of the verification credentials that can be transmitted independently. Instead of requiring continuous server communication or complex verification protocols, the token contains all necessary verification information (signed public key, content hash, timestamp) that can be copied and verified anywhere offline.
2Ease of operation
If offline verification capability is provided to enable content authentication without server communication, then system autonomy and usability are improved, but security risks and verification reliability may deteriorate
Solution Approach 1:
The server acts as a trusted intermediary that signs the device public key, creating a verification chain. The signed data token contains the server-verified public key, which serves as an intermediary credential that recipients can trust without needing direct server communication. This intermediary signature maintains security while enabling offline verification.
Solution Approach 2:
All security verification is performed in advance by the server before content is shared offline. The server signs the public key and creates the verified token beforehand, so that offline recipients can simply verify the pre-established credentials without performing complex security checks or requiring server connectivity.
3Reliability
If comprehensive verification data is stored locally to enable standalone content authentication, then verification independence is improved, but device storage requirements and data management complexity increase
Solution Approach 1:
The essential verification information (signed public key, content hash, timestamp) is extracted from the complex cryptographic verification system and packaged into a compact verified data token. This token contains only the necessary elements for verification, eliminating the need to store large cryptographic datasets or maintain complex verification databases on the device.
Solution Approach 2:
The verification data is transformed from a complex set of cryptographic parameters into a streamlined token format with fixed essential parameters (signed public key, content hash, timestamp). This parameter optimization reduces storage requirements while maintaining verification independence, as the token contains precisely the right amount of data needed for standalone verification.
Data Source
AI summary
In some embodiments, a method of verifying images includes receiving, at a server, a request from a mobile device to sign a device public key of the mobile device; in response to the request from the mobile device, signing, at the server, the device public key with a server private key so as to generate a signed device public key and returning the signed device public key to the mobile device; generating, at the mobile device, data for verification; signing, at the mobile device, the data with a device private key of the mobile device; and storing, at the mobile device, the signed data, the device public key of the mobile device, and the signed device public key of the mobile device as a data token. Numerous other aspects are provided.