Source Code Checksum Metadata for Safety Program Change Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing text-based programming of safety-relevant programs lacks effective measures to detect and prevent unintentional changes, compromising the integrity and security of the programming process.
Innovation Solution
A method that includes adding metadata with checksums to the source code, allowing for the detection of modifications by comparing current and previous checksums, and providing visual and audible alerts to ensure the integrity of the programming process.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If text-based programming is used for safety-relevant programs, then flexibility and ease of editing are improved, but the ability to detect and prevent unintentional changes deteriorates
Solution Approach 1:
The patent applies preliminary action by generating and storing a checksum of the safety-relevant program part before any potential modifications occur. This pre-computed checksum is embedded in the source code as metadata, enabling future comparison to detect any unintentional changes that may happen during text-based editing.
Solution Approach 2:
The patent implements feedback by comparing the current checksum (generated from the current state of the safety-relevant program part) with the previously stored checksum. When a difference is detected, the system provides feedback to the user through an output device, alerting them to the unintentional modification.
2Reliability
If specialized software tools with failsafe packages are used, then security protection is improved, but ease of operation and flexibility deteriorate
Solution Approach 1:
The patent extracts the essential security function (checksum verification) from complex specialized software tools and implements it directly within the text-based programming environment. By embedding the checksum metadata directly in the source code files, the system provides security protection without requiring dedicated specialized tools, thus maintaining user flexibility.
Solution Approach 2:
The patent makes the checksum-based security mechanism universal by applying it to standard text-based programming workflows. The solution works with any text editor and integrates seamlessly into existing development processes, eliminating the need for proprietary failsafe packages while maintaining security protection across different editing environments.
3Measurement precision
If checksum verification is implemented in text-based programming, then detection of modifications is improved, but device complexity increases
Solution Approach 1:
The patent uses checksums as simple, lightweight data structures that require minimal computational resources. The checksum verification process is computationally inexpensive and can be performed quickly without adding significant complexity to the programming system. The metadata embedded in the source code is compact and easy to process.
Data Source
Figure 1~2
AI summary
A computer-implemented method and a device (100) for securing the source code (50) of a safety-related program (40) for operating a control unit (1000), written in at least one text file, is disclosed. The method comprises reading (S100) metadata stored in the source code (50) of the safety-related program (40), wherein the metadata includes a checksum previously stored for a safety-related program part, which is assigned within the source code (50) to a corresponding safety-related program part. The method further comprises generating (S200) a current checksum based on a string of the safety-related program part and detecting (S300) whether the safety-related program part has been modified by comparing the current checksum with the read checksum.Furthermore, an S400 output is sent to the user indicating whether a security-relevant part of the program has been changed in response to the detection of a difference between the compared checksums.