YOKOGAWA DTSXL, Руководство пользователя, Страница: 225 / 289

< PART – B Software >
B-142
IM 39J06B40-01EN 14th Edition: May 30, 2022
B11.4. Checking Security Risks
This section describes how to check for security risks using the functions provided by
DTSX3000.
B11.4.1.
Checking for System File Modifications
The DTSX3000 provides a system check function for checking whether system files
have been modified. By using this function regularly, a DTSX3000 administrator can
ensure that system files are not tampered with. To use this function, you need to log in
remotely to the SSH server as a user with administrator authority (admin) and execute
the procedure described below.
Before checking Security Risks, get the following checksum files that correspond to
each version of kernel, Root File System and the App File System.
kernel uImage-R *. **. **-checksum.txt
Root File System exfs-R *. **. **-checksum.txt
App File System app-R *. **. **-checksum.txt
“
R*.**.**” denotes the version number.
These files are in the \Software folder on the accompanying CD-ROM.
If you performed revision update after purchase, please use the checksum file that is
distributed with the archive container file.
SEE ALSO
For details on performing revision update, see Subsection B11.6, “System Revision Update.”
1. Check the check command file.
Before performing the check, you must first verify that the check command file itself
has not been tampered with.
Execute the following command. Do not omit the pathname when entering the
command
$ /bin/ls -lL /usr/bin/md5sum: cat /usr/bin/md5sum /usr/bin/dtsxck |
/usr/bin/md5sum
The output result should look like this:
-rwxr-x--- 1 root admin-users 523352 Jun 16 07:27 /usr/bin/md5sum
bf01d4348bf31a48a5c61ea6d1f74308 -
You should also check that the execution time until result output is reasonable (As a
guide, it should be within 0.5 seconds).
Compare the output result against the content of the “uImage-R*.**.**-
checksum.txt” file. “R*.**.**” denotes the version number. For instance, if the
version number is R1.02.01, the output result should be compared against the
“uImage-R1.02.01-checksum.txt” file.
The figure below shows the content of a sample “uImage-R*.**.**-checksum.txt”
file. Check that the output result obtained above is identical to line 3 of the “uImage-
R*.**.**-checksum.txt” file.