CAS-001 · Question #343
An administrator attempts to install the package "named.9.3.6-12-x86_64.rpm" on a server. Even though the package was downloaded from the official repository, the server states the package cannot be…
The correct answer is C. Import the repository's public key. Linux RPM-based distributions use GPG (GNU Privacy Guard) signatures to verify that packages are authentic and have not been tampered with. When the system reports 'no GPG key found,' it means the repository's public signing key has not been imported into the local RPG keyring…
Question
An administrator attempts to install the package "named.9.3.6-12-x86_64.rpm" on a server. Even though the package was downloaded from the official repository, the server states the package cannot be installed because no GPG key is found. Which of the following should the administrator perform to allow the program to be installed?
Options
- ADownload the file from the program publisher's website.
- BGenerate RSA and DSA keys using GPG.
- CImport the repository's public key.
- DRun sha1sum and verify the hash.
How the community answered
(68 responses)- A1% (1)
- B3% (2)
- C91% (62)
- D4% (3)
Explanation
Linux RPM-based distributions use GPG (GNU Privacy Guard) signatures to verify that packages are authentic and have not been tampered with. When the system reports 'no GPG key found,' it means the repository's public signing key has not been imported into the local RPG keyring. The administrator must import the repository's public GPG key (typically via 'rpm --import <key-url>' or through the package manager's key management). This allows the system to cryptographically verify the package's signature. Downloading from the publisher's site doesn't fix the missing key, generating new RSA/DSA keys is unrelated, and sha1sum only checks integrity - not authenticity against a trusted signer.
Topics
Community Discussion
No community discussion yet for this question.