LFCS practice question 14 of 35

When using rpm --verify to check files created during the installation of RPM packages, which of the following information is taken into consideration? (Choose THREE correct answers.)

Full set: 260 questions
Answer options
A: Timestamps Correct answer
B: MD5 checksums Correct answer
C: Inodes
D: File sizes Correct answer
E: GnuPG signatures
Correct Answer:
A. Timestamps; B. MD5 checksums; D. File sizes
Explanation

The rpm --verify (or -V) command compares metadata about the installed files of a package against the information stored in the RPM database when the package was installed. This verification process checks for discrepancies in several attributes. Among the attributes checked are the file's modification time (timestamp), its MD5 checksum to ensure content integrity, and its size. These three checks help determine if files have been altered since their initial installation.

Why Incorrect

C. Inode numbers are not checked by rpm --verify. An inode number is a filesystem-specific pointer and can change (e.g., during a backup/restore) without the file's content changing.
E. GnuPG signatures are used to verify the authenticity of the RPM package file itself (rpm -K), not the integrity of the files after they have been installed on the system.

References

1. rpm man page (on any RHEL/CentOS/Fedora system), Section: "VERIFY OPTIONS". It details the output format of rpm -V, where S indicates file Size, 5 indicates MD5 sum, and T indicates mTime (modification time).

2. Red Hat Enterprise Linux 8 Documentation, "Building, running, and managing containers", Section 5.1. "Verifying installed packages". The documentation lists the attributes checked, including "MD5 checksum", "File size", and "Modification timestamp (mtime)".

Scroll to Top