google-chrome changed gpg signing key?

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

google-chrome changed gpg signing key?

ellanios82
  am seeing :


File 'repomd.xml' from repository 'google-chrome' is signed with an
unknown key '1397BC53640DB551'


  regards

....



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

nicholas cunliffe
same here, raised issue on forums. installing the key again from
google site results in the same unknown key result.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

John Andersen-2
In reply to this post by ellanios82
On 07/27/2017 12:58 PM, ellanios82 wrote:

>  am seeing :
>
>
> File 'repomd.xml' from repository 'google-chrome' is signed with an unknown key '1397BC53640DB551'
>
>
>  regards
>
> ....
>
>
>

https://www.google.com/linuxrepositories/

Command line key installation for RPM

On an RPM-based system (Fedora, SUSE, Mandriva, RHEL, etc.), download the key and then use rpm to
install it.

wget https://dl.google.com/linux/linux_signing_key.pub
sudo rpm --import linux_signing_key.pub
You can verify the key installation by running:

rpm -qi gpg-pubkey-7fac5991-*


--
After all is said and done, more is said than done.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

John Andersen-2
In reply to this post by nicholas cunliffe
On 07/27/2017 01:53 PM, nicholas cunliffe wrote:
> same here, raised issue on forums. installing the key again from
> google site results in the same unknown key result.
>

The key does check out, according to Kleopatra's check:

0x1397BC53640DB551

This certificate is currently valid.
User-ID:
Google Inc. (Linux Packages Signing Authority) <[hidden email]>
Validity:
from 4/11/16 10:51 PM until forever
Certificate type:
4096-bit RSA
Certificate usage:

Key-ID:
D38B4796
Fingerprint:
EB4C1BFD4F042F6DDDCCEC917721F63BD38B4796
Ownertrust:
unknown
Stored:
on this computer

So that leaves some questions about which keyserver zypper is using
or some other problem with with yast/zypp and friends.
The repository I uses points direct to Google.

--
After all is said and done, more is said than done.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

Carlos E. R.-2
On 2017-07-28 00:17, John Andersen wrote:
> On 07/27/2017 01:53 PM, nicholas cunliffe wrote:


> So that leaves some questions about which keyserver zypper is using

None. It doesn't use keyservers.

--
Cheers / Saludos,

                Carlos E. R.

  (from 42.2 x86_64 "Malachite" (Minas Tirith))


signature.asc (220 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

nicholas cunliffe
In reply to this post by ellanios82
On 27 July 2017 at 23:47, Tom Wroblewski <[hidden email]> wrote:

> This worked for me:
>
> wget https://dl.google.com/linux/linux_signing_key.pub
> sudo rpm --import linux_signing_key.pub
>
> you can verify the key by running:
>
> rpm -qi gpg-pubkey-7fac5991-*
>
> these commands came from here: https://www.google.com/linuxrepositories/

to check we are discussing the same issue - you had chrome installed,
everything worked, a few days ago you suddenly got the key signing
problem, you carried out the above install and *now everything is
OK?*. I carried out the above exact steps and still the key issue
remains.

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

ellanios82
In reply to this post by John Andersen-2
On 28/07/17 01:08, John Andersen wrote:
> wgethttps://dl.google.com/linux/linux_signing_key.pub
> sudo rpm --import linux_signing_key.pub
> You can verify the key installation by running:
>
> rpm -qi gpg-pubkey-7fac5991-*


  - thanks . . . done that . . . but still get error :


File 'repomd.xml' from repository 'google-chrome' is signed with an
unknown key '1397BC53640DB551'


...

  regards



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

Richmond-2
ellanios82 <[hidden email]> writes:

> On 28/07/17 01:08, John Andersen wrote:
>> wgethttps://dl.google.com/linux/linux_signing_key.pub
>> sudo rpm --import linux_signing_key.pub
>> You can verify the key installation by running:
>>
>> rpm -qi gpg-pubkey-7fac5991-*
>
>
>  - thanks . . . done that . . . but still get error :
>
>
> File 'repomd.xml' from repository 'google-chrome' is signed with an unknown
> key '1397BC53640DB551'
>
>

I am getting this error too. I tried the rpm commands and I tried:

gpg --recv-keys 1397BC53640DB551

Which says:

gpg: requesting key 640DB551 from hkp server keys.gnupg.net
gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority)
<[hidden email]>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

But then sudo zypper refresh says:

File 'repomd.xml' from repository 'google' is signed with an unknown key
'1397BC53640DB551'. Continue? [yes/no] (no):

gpg -k

gpg -k|grep -i google
uid       [ unknown] Google Inc. (Linux Packages Signing Authority)
<[hidden email]>

Shows it is unknown.

So I changed the trust using gpg --key-edit

gpg -k|grep -i google
uid       [ultimate] Google Inc. (Linux Packages Signing Authority)
<[hidden email]>

But I still get the error.

This all seems wrong anyway, I need to verify the key somehow, not
blindly trust it.

--
~


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

Carlos E. R.-2
On 2017-08-09 22:47, Richmond wrote:

> I am getting this error too. I tried the rpm commands and I tried:
>
> gpg --recv-keys 1397BC53640DB551
>
> Which says:
>
> gpg: requesting key 640DB551 from hkp server keys.gnupg.net
> gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority)
> <[hidden email]>" not changed
> gpg: Total number processed: 1
> gpg:              unchanged: 1
AFAIK rpm/zypper do not import the keys that way. It is also not stored
in the same place for command gpg than for rpm.

--
Cheers / Saludos,

                Carlos E. R.
                (from 42.2 x86_64 "Malachite" at Telcontar)


signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

Marcus Meissner
Hi,

This is a problem in libzypp. It will be addressed by an update of
libzypp.

Ciao, Marcus
On Thu, Aug 10, 2017 at 03:58:17PM +0200, Carlos E. R. wrote:

> On 2017-08-09 22:47, Richmond wrote:
>
> > I am getting this error too. I tried the rpm commands and I tried:
> >
> > gpg --recv-keys 1397BC53640DB551
> >
> > Which says:
> >
> > gpg: requesting key 640DB551 from hkp server keys.gnupg.net
> > gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority)
> > <[hidden email]>" not changed
> > gpg: Total number processed: 1
> > gpg:              unchanged: 1
>
> AFAIK rpm/zypper do not import the keys that way. It is also not stored
> in the same place for command gpg than for rpm.
>
> --
> Cheers / Saludos,
>
> Carlos E. R.
> (from 42.2 x86_64 "Malachite" at Telcontar)
>




--
Marcus Meissner,SUSE LINUX GmbH; Maxfeldstrasse 5; D-90409 Nuernberg; Zi. 3.1-33,+49-911-740 53-432,,serv=loki,mail=wotan,type=real <[hidden email]>

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

Carlos E. R.-2
On 2017-08-10 16:00, Marcus Meissner wrote:
> Hi,
>
> This is a problem in libzypp. It will be addressed by an update of
> libzypp.

To clarify:

Bugzilla – Bug 1008325
Zypp fails to handle repositories signed with a GPG subkey

--
Cheers / Saludos,

                Carlos E. R.
                (from 42.2 x86_64 "Malachite" at Telcontar)


signature.asc (188 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

George from the tribe
In reply to this post by Marcus Meissner
On 08/10/2017 10:00 PM, Marcus Meissner wrote:
> Hi,
>
> This is a problem in libzypp. It will be addressed by an update of
> libzypp.
>
> Ciao, Marcus

Ok, good to know. I was wondering what progress had been made on the error.

--
George
Box:       42.2 | KDE Plasma 5.8 | AMD Phenom IIX4 | 64 | 32GB
Laptop #1: 42.2 | KDE Plasma 5.8 | AMD FX 7TH GEN  | 64 | 32GB
Laptop #2: 42.2 | KDE Plasma 5.8 | Core i5         | 64 | 8GB


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

ellanios82
In reply to this post by Marcus Meissner
On 10/08/17 17:00, Marcus Meissner wrote:

> Hi,
>
> This is a problem in libzypp. It will be addressed by an update of
> libzypp.
>
> Ciao, Marcus
> On Thu, Aug 10, 2017 at 03:58:17PM +0200, Carlos E. R. wrote:
>> On 2017-08-09 22:47, Richmond wrote:
>>
>>> I am getting this error too. I tried the rpm commands and I tried:
>>>
>>> gpg --recv-keys 1397BC53640DB551
>>>
>>> Which says:
>>>
>>> gpg: requesting key 640DB551 from hkp server keys.gnupg.net
>>> gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority)
>>> <[hidden email]>" not changed
>>> gpg: Total number processed: 1
>>> gpg:              unchanged: 1
>> AFAIK rpm/zypper do not import the keys that way. It is also not stored
>> in the same place for command gpg than for rpm.
>>
>> --
>> Cheers / Saludos,
  - thank you kindly Marcus :

Today's zypper dup, with new libzypp , sadly did not yet fix this problem

regards
......

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

ellanios82
On 20/08/17 17:02, ellanios82 wrote:

> On 10/08/17 17:00, Marcus Meissner wrote:
>> Hi,
>>
>> This is a problem in libzypp. It will be addressed by an update of
>> libzypp.
>>
>> Ciao, Marcus
>> On Thu, Aug 10, 2017 at 03:58:17PM +0200, Carlos E. R. wrote:
>>> On 2017-08-09 22:47, Richmond wrote:
>>>
>>>> I am getting this error too. I tried the rpm commands and I tried:
>>>>
>>>> gpg --recv-keys 1397BC53640DB551
>>>>
>>>> Which says:
>>>>
>>>> gpg: requesting key 640DB551 from hkp server keys.gnupg.net
>>>> gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority)
>>>> <[hidden email]>" not changed
>>>> gpg: Total number processed: 1
>>>> gpg:              unchanged: 1
>>> AFAIK rpm/zypper do not import the keys that way. It is also not stored
>>> in the same place for command gpg than for rpm.
>>>
>>> --
>>> Cheers / Saludos,
>  - thank you kindly Marcus :

  - as yet , this  google-chrome problem with gpg signing key is still
to be fixed

  regards
....



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: google-chrome changed gpg signing key?

ellanios82
In reply to this post by Marcus Meissner
On 10/08/17 17:00, Marcus Meissner wrote:

> Hi,
>
> This is a problem in libzypp. It will be addressed by an update of
> libzypp.
>
> Ciao, Marcus
> On Thu, Aug 10, 2017 at 03:58:17PM +0200, Carlos E. R. wrote:
>> On 2017-08-09 22:47, Richmond wrote:
>>
>>> I am getting this error too. I tried the rpm commands and I tried:
>>>
>>> gpg --recv-keys 1397BC53640DB551
>>>
>>> Which says:
>>>
>>> gpg: requesting key 640DB551 from hkp server keys.gnupg.net
>>> gpg: key D38B4796: "Google Inc. (Linux Packages Signing Authority)
>>> <[hidden email]>" not changed
>>> gpg: Total number processed: 1
>>> gpg:              unchanged: 1
>> AFAIK rpm/zypper do not import the keys that way. It is also not stored
>> in the same place for command gpg than for rpm.
>>
>> --
>> Cheers / Saludos,
  - google-chrome gpg signing key :

  this is Fixed ok by latest "zypper dup" : Thanks all

......
  regards


--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]