content_image/781800.jpg content_image/781809.jpg
<img src='content_image/781800.jpg'>

The Section 2.1.4.2, “Signature Checking Using GnuPG” , section explains why you do not see a green Good signature  result. 

## 2.1.4.4 Signature Checking Using RPM 

For RPM packages, there is no separate signature. RPM packages have a built-in GPG signature and MD5 checksum. You can verify a package by running the following command: 

shell> rpm --checksig package_name .rpm 

Example: 

shell> rpm --checksig MySQL-server-8.0.25-0.linux_glibc2.5.i386.rpm MySQL-server-8.0.25-0.linux_glibc2.5.i386.rpm: md5 gpg OK 

<img src='content_image/781809.jpg'>

shell> gpg --export -a 5072e1f5 > 5072e1f5.asc shell> rpm --import 5072e1f5.asc 

## Note 

If you are using RPM 4.1 and it complains about (GPG) NOT OK (MISSING KEYS: GPG#5072e1f5) , even though you have imported the MySQL public build key into your own GPG keyring, you need to import the key into the RPM keyring first. RPM 4.1 no longer uses your personal GPG keyring (or GPG itself). Rather, RPM maintains a separate keyring because it is a system-wide application and a user’s GPG public keyring is a user-specific file. To import the MySQL public key into the RPM keyring, first obtain the key, then use rpm --import  to import the key. For example: 

