ACPI administration advocacy advocacy advocacy opinion alsa apache apple apt aptitude audio authentication awk bash business cache calendar censorship commandline cron database debian desktop development disk dvd economics emacs email europe exim files firefox firewall flash foss freedom ftp fun git grub hardware hardware html images installation ipod kde kernel keyboard knoppix laptop latex locale lockin longlines microsoft mplayer multimedia mysql network nfs openbox openoffice opinion opinion partition pdf perl php politics postgresql printing privacy rant rxvt script scripting scsi security sed server shell siteadmin sitenews sitesoftware skype skype slackware sound spam ssh subversion sudo svk swap t23 t43 terminal text thinkpad thunderbird time timezone ubuntu users versioncontrol video windows wine wordpress wordprocessing xwindows xwindows youtube
I've been getting this error recently:
W: There is no public key available for the following key IDs: 9AA38DCD55BE302B W: There is no public key available for the following key IDs: 9AA38DCD55BE302B W: GPG error: http://ftp.cz.debian.org etch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9AA38DCD55BE302B W: You may want to run apt-get update to correct these problems
The way to fix it was to run these commands:
gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 9AA38DCD55BE302B sudo apt-key add ~/.gnupg/pubring.gpg sudo apt-get update
Is this really a good idea? Adding the key from a public key server? Why even use GPG in the first place if we're just going to go add keys we don't have from sources that anyone can contribute to?
Posted by Blah on 2009-06-24 15:27:11.