Embedded Configuration File Signing With Parent Security Elements
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing configuration file management systems for devices, particularly in complex automation systems, are inefficient and resource-intensive due to the need for extensive cryptographic operations and organizational overhead, especially when dealing with multiple files and ensuring compatibility and integrity.
Innovation Solution
A method involving a parent file that embeds configuration subfiles with their respective security elements, using only metadata and security elements of these subfiles to create a parent file security element, reducing the computational effort required for signing and ensuring integrity and authenticity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If configuration files are compiled from multiple configuration files with digital signatures and manifests, then integrity and authenticity are ensured, but computational effort and resource usage increase significantly
Solution Approach 1:
The patent embeds configuration files directly within the manifest file structure, creating a nested hierarchy where subfiles are contained within the parent manifest. This nesting eliminates the need for separate file handling and multiple signature operations, as the embedded structure allows the manifest signature to cover all contained configuration files in a single cryptographic operation.
Solution Approach 2:
The patent combines multiple configuration files and the manifest into a single unified file structure. By merging the configuration files within the manifest and using a single parent file signature to authenticate the entire bundle, the system reduces multiple separate cryptographic operations into one consolidated signing and verification process.
2Reliability
If multiple configuration files are managed separately with individual signatures, then file integrity is verified, but organizational overhead and complexity increase
Solution Approach 1:
The patent merges multiple configuration files and their metadata into a single manifest structure, eliminating the need to manage separate signature files and manifest files. The unified structure contains all configuration data and authentication information in one place, simplifying the organizational overhead.
Solution Approach 2:
The manifest file serves multiple functions simultaneously: it acts as a container for configuration files, a metadata repository, and an authentication mechanism through its digital signature. This multi-functionality eliminates the need for separate files for each purpose, reducing complexity.
3Reliability
If configuration bundles include all configuration files and manifests, then complete configuration is provided, but file size and resource requirements increase
Solution Approach 1:
The patent embeds configuration files directly within the manifest file structure, creating a compact nested hierarchy. This nesting eliminates redundant file headers, metadata repetition, and separate file formatting overhead, reducing the total file size while maintaining complete configuration data.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method is described which comprises: i) providing a parent file (100) for a control panel, wherein the parent file (100) comprises: metadata (160), an embedded first subfile (110), an embedded second subfile (120), a first security element (111, 112) with respect to the first subfile (110), and a second security element (121, 122) with respect to the second subfile (120); and ii) creating a parent file security element (101), in particular exclusively, based on: a) at least some part of the metadata (160) of the parent file (100), b) the first security element (111, 112), and c) the second security element (121, 122).