DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I know this is not really a serious issue, but I'd still like to avoid this issue:
Quote:
W: GPG error: http://mirror.pacific.net.au testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F
W: GPG error: http://repos.knio.it testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY CBE5831435A92053
W: GPG error: http://secure-testing.debian.net etch/security-updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 946AA6E18722E71E
W: GPG error: ftp://ftp.nerim.net etch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 07DC563D1F41B907
W: GPG error: ftp://mirrors.kernel.org testing Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 010908312D230C5F
From where do I download the public key to these packages for use in Synaptic and apt-get.
I have installed KGpg which should simplify the GPG part. However, I'd just like to know where these keys can be downloaded from and used for apt.
I have read that site before, I think you linked to it in another thread. Actually, what I don't understand is where to download the public keys for these repositories.
Also I use KGpg. So I don't need the exact commands, just the location where to download the key...
Sorry if I sound a bit vague, but that's what comes out of half-knowledge
I have read that site before, I think you linked to it in another thread. Actually, what I don't understand is where to download the public keys for these repositories.
Also I use KGpg. So I don't need the exact commands, just the location where to download the key...
Sorry if I sound a bit vague, but that's what comes out of half-knowledge
For getting the keys you use gpg so for the first one you do not have try as root.
Now repeat for each of the keys you need and hopefully all of them have been uploaded to a keyserver that the mit.edu mirrors on their keyserver. If not then most times if you put in the url of the repository you will find an archive.key or a file ending in .asc this would be the file you need then you would use gpg --import http://www.????.LLL/path/to/archive.key then use the --export to put it into the apt keyring you only need the last eight letters/numbers when exporting you can find these by using the gpg --list-keys and it will show you them.
I understand that part about import the key into GPG and then exporting it for use with apt-key. The problem is finding the .asc file for each repository... Is there any other way to "auto-detect" the public key file for each repository?
Yah, I successfully managed to import all the keys using the technique of searching for the key ID rather than the .asc file. I used KGpg anyway, since I didn't want to type in every command using gpg. It's actually very easy to use.
Thanks for pointing me in the right direction. Now all the errors regarding GPG no longer exist.
Earlier the importing from a key server wasn't working because of a firewall issue. I now allowed the firewall (guarddog) to connect to pgp key servers and it works fine. That was where the confusion lay.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.