LFCS · Question #819
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.)
The correct answer is A. Timestamps B. MD5 checksums D. File sizes. The rpm --verify command checks the integrity of installed package files by comparing their current attributes against metadata, including timestamps, MD5 checksums, and file sizes.
Question
Options
- ATimestamps
- BMD5 checksums
- CInodes
- DFile sizes
- EGnuPG signatures
How the community answered
(46 responses)- A91% (42)
- C4% (2)
- E4% (2)
Why each option
The `rpm --verify` command checks the integrity of installed package files by comparing their current attributes against metadata, including timestamps, MD5 checksums, and file sizes.
The `rpm --verify` command checks the modification time (timestamp) of files to detect if they have been altered since installation.
MD5 checksums (or other cryptographic checksums) are a core part of `rpm --verify` to ensure the file content has not been corrupted or tampered with.
Inodes are internal filesystem data structures that track file location and metadata, but `rpm --verify` does not directly verify inode numbers as part of its integrity checks.
File sizes are checked by `rpm --verify` to identify discrepancies that might indicate a file has been partially overwritten or corrupted.
GnuPG signatures are used to verify the authenticity and integrity of the RPM *package file itself* before installation, not the individual files after they have been extracted and installed by `rpm --verify`.
Concept tested: RPM package file verification
Source: https://man7.org/linux/man-pages/man8/rpm.8.html
Topics
Community Discussion
No community discussion yet for this question.