CAS-003 · Question #192
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. RPM-based Linux distributions use GPG signatures to verify package authenticity and integrity. When you attempt to install a package and the system reports 'no GPG key found,' it means the GPG public key used by the repository to sign that package is not present in the system's…
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
(46 responses)- A7% (3)
- B2% (1)
- C89% (41)
- D2% (1)
Explanation
RPM-based Linux distributions use GPG signatures to verify package authenticity and integrity. When you attempt to install a package and the system reports 'no GPG key found,' it means the GPG public key used by the repository to sign that package is not present in the system's trusted keyring. The correct fix is to import the repository's public GPG key (e.g., using 'rpm --import' or the package manager's key import command). This allows RPM to verify the package's signature and proceed with installation. Downloading from the publisher's website does not resolve the missing key issue. Generating new RSA/DSA keys creates new keys, not the repository's existing key. Running sha1sum only checks file integrity, not signature authenticity.
Topics
Community Discussion
No community discussion yet for this question.