Oracle 5.0, Reference Manual

Page: 74 / 3232

Signature Checking Using
Gpg4win
for Windows
54
Select the "MySQL Release Engineering" certificate. The Fingerprint and Key-ID must be "5072E1F5",
or choose Details... to confirm the certificate is valid. Now, import it by clicking Import. An import dialog
will be displayed, choose Okay, and this certificate will now be listed under the Imported Certificates
tab.
Next, configure the trust level for our certificate. Select our certificate, then from the main menu select
Certificates, Change Owner Trust.... We suggest choosing I believe checks are very accurate for our
certificate, as otherwise you might not be able to verify our signature. Select I believe checks are very
accurate and then press OK.
Figure 2.3. Changing the Trust level
Next, verify the downloaded MySQL package file. This requires files for both the packaged file, and
the signature. The signature file must have the same name as the packaged file but with an appended
.asc
extension, as shown by the example in the following table. The signature is linked to on the
downloads page for each MySQL product. You must create the
.asc
file with this signature.
Table 2.2. MySQL Package and Signature Files for MySQL Installer for Microsoft Windows
File Type File Name
Distribution file
mysql-installer-community-5.0.96.msi
Signature file
mysql-installer-community-5.0.96.msi.asc
Make sure that both files are stored in the same directory and then run the following command to verify
the signature for the distribution file. Either drag and drop the signature (
.asc
) file into Kleopatra, or
load the dialog from File, Decrypt/Verify Files..., and then choose either the
.msi
or
.asc
file.