Shulou(Shulou.com)06/01 Report--

This article focuses on "CentOS installation of rpm packages encountered Header V3 DSA signature: NOKEY how to solve", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to solve the problem of Header V3 DSA signature: NOKEY when CentOS installs the rpm package.

After minimizing installation, you will often encounter when installing rpm packages

The code is as follows:

Warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID*

This is due to the fact that yum installed an old version of GPG keys, and the solution is

The code is as follows:

Rpm--import / etc/pki/rpm-gpg/RPM*

Linux/centos Header V3 DSA signature: NOKEY, key ID error resolution

Add-- force-- nodeps such as

# rpm-ivh db4-devel-4.3.29-9.fc6.i386.rpm-force-nodeps

It's really strange that the RPM files that can be installed directly on the system can no longer be installed now. Double-click directly to run them, that is, they will automatically withdraw after a while of waiting.

Come out, so come to the terminal to have a look!

Rpm-ivh * .rpm

Results: V3 DSA signature: BAD, key ID....

Package * .rpm is not installed

Send a short message to the reviewer

I see. When making inquiries on the Internet, some say that they are checked for errors and need to be downloaded again, but what is depressing is that the software of the last system is all good, how could it happen?

What about all the check errors?

Finally, I saw another method on the Internet: the error resolution was added after the rpm command-- force-- nodeps, that is, forced installation.

I haven't tried it yet. I don't know if it's useful. I'll continue after using it.

I tried it when I came home from work, but it didn't work. It was the same mistake. Later, I saw a passage like this on a website:

Starting with RPM version 4.1, the signature of the package is checked when you install or upgrade the package. If the signature verification fails, you will see the following

Error message of:

Error: V3 DSA signature: BAD, key ID 0352860f

If it is a new, header-only signature, you will see an error message like this:

Error: Header V3 DSA signature: BAD, key ID 0352860f

If you do not install the appropriate key to verify the signature, the message will include NOKEY, such as:

Warning: V3 DSA signature: NOKEY, key ID 0352860f

Under CentOS, sometimes when you install software with yum, you will end up with a prompt:

Quote

Warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID*

This is due to the fact that yum installed an old version of GPG keys, and the solution is

Quote

Rpm--import / etc/pki/rpm-gpg/RPM*

If you install the software again, you won't have this error message.

At this point, I believe that everyone has a deeper understanding of "CentOS encountered Header V3 DSA signature: NOKEY how to solve the problem when installing the Header package". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.