LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (http://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Public Key for NetworkManager (http://www.linuxquestions.org/questions/linux-newbie-8/public-key-for-networkmanager-710497/)

majorlinux 03-10-2009 09:42 AM

Public Key for NetworkManager
 
When I tried updating Fedora 10 this morning, both with yum and with the graphical updater, I have been getting this error:

Code:

warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 4ebfc273


Public key for NetworkManager-glib-0.7.0.99-3.fc10.i386.rpm is not installed

Does anyone know what this means and how to fix it? Its only hindering the updates, but I would really like to get it fixed ASAP.

fierywater 03-10-2009 10:21 AM

I'm having the same problem with my Fedora 10 updater. Same file, same error. I'll let you know if I come up with anything.

vonedaddy 03-10-2009 10:30 AM

I can not offer an explanation but I can tell you how to get around it.


Code:

yum --nogpgcheck update

24seven 03-10-2009 10:43 AM

Worked for me.

Though it might be safer to allow the PGP check on the other updates:
Code:

yum --nogpgcheck update NetworkManager
yup update


shaolin77 03-10-2009 11:18 AM

Quote:

Originally Posted by 24seven (Post 3470821)
Worked for me.

Though it might be safer to allow the PGP check on the other updates:
Code:

yum --nogpgcheck update NetworkManager
yup update


I'm getting the following when attempting to update
:
Public key for NetworkManager-glib-0.7.0.99-3.fc10.i386.rpm is not installedv

and I ended up bypassing the following:


NetworkManager VPN plugin for OpenVPN
NetworkManager VPN plugin for vpnc
Libraries for adding NetworkManager support to applications that use glib
GNOME applications for use with NetworkManager
Network connection manager and user applications

so that the other updates can be applied...I've seen others are having the same issue on the other forums.. once resolve you can apply the updates that have not been applied, but at least you have the others installed if you bypass the following mentioned above.

spurster 03-10-2009 12:27 PM

Maybe a messed up signature
 
When I do:

Code:

rpm -qip NetworkManager-0.7.0.99-3.fc10.i386.rpm
One of the lines starts with:

Code:

Signature  : DSA/8
On other .rpm files that I have checked, the same line starts with:

Code:

Signature  : DSA/SHA1
I think I will wait before I force this update.

custangro 03-10-2009 02:05 PM

FWIW...

I found this to be helpful....

Code:

root@fedora# yum -y update  --nogpgcheck
-C

JulianTosh 03-10-2009 05:14 PM

A safer method (for now) is to exclude NetworkManager* until we figure out why the signature does not work:

Code:

yum -y -x NetworkManager* update

keith langett 03-10-2009 06:22 PM

Hey!! Thanks for the thread to help me update the public key on my FC10 box. this really worked >>
yum --nogpgcheck update NetworkManager
yup update

Keith langett

UncleBubba 03-10-2009 07:01 PM

Be Careful About Bypassing The GPG Check
 
Y'all be careful about bypassing the GPG signature check on update packages. While this one is probably an innocent error, a failed signature check could indicate a package that was changed after it was signed.

If that's the case, you really have no way of knowing what is in the package you're installing on your system--it could be anything.

Just be careful...

custangro 03-10-2009 07:21 PM

Quote:

Originally Posted by UncleBubba (Post 3471274)
Y'all be careful about bypassing the GPG signature check on update packages. While this one is probably an innocent error, a failed signature check could indicate a package that was changed after it was signed.

If that's the case, you really have no way of knowing what is in the package you're installing on your system--it could be anything.

Just be careful...

Yes, you are right! And I would _never_ do this on a production machine....EVER

That being said...

I have Fedora 10 installed on my laptop that has nothing that I will miss...it's my "messing around" machine...

But you are right UncleBubba... BE CAREFUL!

-C

majorlinux 03-10-2009 11:35 PM

Quote:

Originally Posted by vonedaddy (Post 3470807)
I can not offer an explanation but I can tell you how to get around it.


Code:

yum --nogpgcheck update

This worked for me as well. Will be careful about the unsigned packages. Thanks everyone for helping me out with that.

jman82s 03-11-2009 02:34 AM

For anyone confused, it was indeed an innocent error:

"Hi

Release Engineering team has the following announcement:

"Several of you have reported issues with the F-9 and F-10
NetworkManager updates that were pushed last night (March 9)
related to an incorrect GPG key. The error output looked like:

Public key for NetworkManager-0.7.0.99-3.fc10.i386.rpm is not installed

However the key it was signed with was apparently the proper F9 or F10
GPG key.

This issue has been resolved for F-10 updates, and will be resolved for
F-9 updates relatively soon. In an effort for full discloser, I've
included a description of the events that caused this below."

More here: https://www.redhat.com/archives/fedo.../msg00004.html

I held off on updating until I had an official explanation.

24seven 03-11-2009 09:05 AM

Quote:

Originally Posted by jman82s (Post 3471519)
For anyone confused, it was indeed an innocent error:

"Hi

Release Engineering team has the following announcement:

"Several of you have reported issues with the F-9 and F-10
NetworkManager updates that were pushed last night (March 9)
related to an incorrect GPG key. The error output looked like:

Public key for NetworkManager-0.7.0.99-3.fc10.i386.rpm is not installed

However the key it was signed with was apparently the proper F9 or F10
GPG key.

This issue has been resolved for F-10 updates, and will be resolved for
F-9 updates relatively soon. In an effort for full discloser, I've
included a description of the events that caused this below."

More here: https://www.redhat.com/archives/fedo.../msg00004.html

I held off on updating until I had an official explanation.

Confirmed - a normal update is now possible

UncleBubba 03-11-2009 05:08 PM

Yep, seems all better now.
 
I was able to successfully update three F10 systems without incident. I also checked several--but by no means all--of the distribution mirrors and saw no trace of the old package.

I did have one problem when yum apparently tried to use the copy already in its cache to do the update. Running the following from the command line deletes non-installed packaged from the cache and resolved the problem for me (and may save someone some time):

sudo yum clean packages

(Yeah, I thought yum would detect the updated server package automatically but I don't want to spend time figuring out whether it was yum or a loose nut behind my keyboard...)


All times are GMT -5. The time now is 10:48 AM.