MySQL :: MySQL 5.0 Reference Manual :: 2.4.5.3 Signature Checking Using RPM, provided by Pantek

Hosting Provided By

Documentation Library
- Table of Contents
  - MySQL 6.0 Reference Manual
  - MySQL 5.1 Reference Manual
  - MySQL 5.0 Reference Manual
  - MySQL 3.23/4.0/4.1 Manual

Additional languages

MySQL 5.0 Reference Manual :: 2 Installing and Upgrading MySQL :: 2.4 Installing MySQL Community Server :: 2.4.5 Verifying Package Integrity Using MD5 Checksums or GnuPG :: 2.4.5.3 Signature Checking Using RPM

« 2.4.5.2 Signature Checking Using GnuPG

2.4.6 Installation Layouts »

Section Navigation [Toggle]

2.4.5 Verifying Package Integrity Using MD5 Checksums or GnuPG
2.4.5.1 Verifying the MD5 Checksum
2.4.5.2 Signature Checking Using GnuPG
2.4.5.3 Signature Checking Using RPM

2.4.5.3.Â Signature Checking Using `RPM`

This section does not apply to MySQL Enterprise Server users.

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-5.0.64-0.glibc23.i386.rpm
MySQL-server-5.0.64-0.glibc23.i386.rpm: md5 gpg OK

Note

If you are using RPM 4.1 and it shows the error (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, it maintains its own 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 as described in SectionÂ 2.4.5.2, â€œSignature Checking Using GnuPGâ€. Then use rpm --import to import the key. For example, if you have saved the public key in a file named mysql_pubkey.asc, import it using this command: