Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

repository keyring

New to Debian (Or Linux in general)? Ask your questions here!
Post Reply
Message
Author
3f31d8d9e4
Posts: 3
Joined: 2017-09-16 09:16

repository keyring

#1 Post by 3f31d8d9e4 »

Hello to the community,

At first, I am sorry in advance if my English is not as good as I would like. This isn't my native language.

I recently turn my computer into Debian. It work well, but there is just one little problem with repository keyring.
When I launch a “sudo apt-get update” command, I always have the message

Code: Select all

W: http://security.debian.org/dists/stretch/updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by user '_apt' executing apt-key.
Here I put http://security.debian.org/dists/stretc ... /InRelease, but it happen with all my repositories.

So, I changed the rights of trusted.gpg. Only the root was allowed to read an write it. Now everybody can read it.
The message changed for :

Code: Select all

W: Impossible to get http://ftp.fr.debian.org/debian/dists/stretch/Release.gpg  The following signatures haven't been verified because the public key isn't available  : NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY EF0F382A1A7B6500 [retranslated to English, the original message can be slightly different]
Thank for your help.

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: repository keyring

#2 Post by debiman »

your english is fine.

the warning is just a warning and as a newbie i wouldn't try to fix what isn't broken.

anyhow, there's a rather recent forum thread about that exact message. try to find it!

3f31d8d9e4
Posts: 3
Joined: 2017-09-16 09:16

Re: repository keyring

#3 Post by 3f31d8d9e4 »

Thank,
Yes, but it like my OS to look clean.
I have to admit, I searched on Qwant and Google, but not on the forum. So they just deleted the gpg file. By security I only renamed it “*.old”.
Now, the main repositories work well. I still have the message for third-parties repositories.

Post Reply