-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I get an unknown GPG key warning, twice, when zypper or yast tries to check for updates. I did this: wget https://dl.google.com/linux/linux_signing_key.pub sudo rpm --import linux_signing_key.pub And now I get one warning, so there is another key that is missing: Unknown GnuPG Key The file repomd.xml (http://dl.google.com/linux/chrome/rpm/stable/x86_64) is digitally signed with the following unknown GnuPG key: ID: 4EB27DB2A3B88B8B. This means that a trust relationship to the creator of the file cannot be established. Using the file may put the integrity of your system at risk. Use it anyway? [ ] Do not show this message again. Where can I download that missing key from? Or is the command secuence I run incomplete or incorrect? (Leap 15.3) - -- Cheers Carlos E. R. (from 15.3 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYvKibxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVaJEAoInpGLur54g7iTRWFj6F SrwlFwsfAJ0YFvwAKKzpAe8rTX5jXVzlPqKD9A== =5ups -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oops. Forgot the subject line. On Tuesday, 2022-08-09 at 20:07 +0200, Carlos E. R. wrote:
I get an unknown GPG key warning, twice, when zypper or yast tries to check for updates. I did this:
wget https://dl.google.com/linux/linux_signing_key.pub sudo rpm --import linux_signing_key.pub
And now I get one warning, so there is another key that is missing:
Unknown GnuPG Key
The file repomd.xml (http://dl.google.com/linux/chrome/rpm/stable/x86_64) is digitally signed with the following unknown GnuPG key: ID: 4EB27DB2A3B88B8B.
This means that a trust relationship to the creator of the file cannot be established. Using the file may put the integrity of your system at risk.
Use it anyway?
[ ] Do not show this message again.
Where can I download that missing key from? Or is the command secuence I run incomplete or incorrect?
(Leap 15.3)
-- Cheers
Carlos E. R. (from 15.3 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYvKllxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV+9sAn3dAf7/i27nXPmDp8VqX bcMyQA9SAJ9Dl7dAIZybqGSlYyv/OPv+BGEoTA== =yrxU -----END PGP SIGNATURE-----
On 2022-08-09 20:21, Carlos E. R. wrote:
On Tuesday, 2022-08-09 at 20:07 +0200, Carlos E. R. wrote:
I get an unknown GPG key warning, twice, when zypper or yast tries to check for updates. I did this:
wget https://dl.google.com/linux/linux_signing_key.pub sudo rpm --import linux_signing_key.pub
And now I get one warning, so there is another key that is missing:
Unknown GnuPG Key
The file repomd.xml (http://dl.google.com/linux/chrome/rpm/stable/x86_64) is digitally signed with the following unknown GnuPG key: ID: 4EB27DB2A3B88B8B.
This means that a trust relationship to the creator of the file cannot be established. Using the file may put the integrity of your system at risk.
Use it anyway?
[ ] Do not show this message again.
Where can I download that missing key from? Or is the command secuence I run incomplete or incorrect?
Information found here: <https://forums.opensuse.org/showthread.php/542491-Zypper-refuses-to-acknowledge-that-I-have-imported-Google-s-latest-signing-key/page2> This sequence seems to work: Telcontar:~ # rpm -e gpg-pubkey-7fac5991-4615767f Telcontar:~ # rpm -e gpg-pubkey-d38b4796-570c8cd3 Telcontar:~ # rpm --import https://dl.google.com/linux/linux_signing_key.pub Telcontar:~ # zypper ref --force google-chrome Forcing raw metadata refresh Retrieving repository 'EXT: google-chrome' metadata .....................................................................................................................................................[done] Forcing building of repository cache Building repository 'EXT: google-chrome' cache ..........................................................................................................................................................[done] Specified repositories have been refreshed. Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
participants (1)
-
Carlos E. R.