same here. (re)loaded the public signing key like you did. still unknown key.
downloaded the rpm from Google (got version 60.x, had version 59.x) and forced (re)install with zypper. re-install from rpm file did not add google-chrome repository. manually (re)added repo, still unknown key.
checked key ID with web search and it appears to be fully legitimate and in existence for years.
re-ran zypper refresh, shrugged, and answered “yes” to the question “Continue?”.
the post you link appears to carry no information regards the current issue? The link regards installation and further comments suggest adding the key to prevent security warnings. In my case I had a working system with key, that suddenly started giving warnings and adding the key again does not help. (or please explain if i havnt understood).
In my experience I am given an option during the install to “ignore” the key error and that’s the end of it.
Even so I just now uninstalled Chrome and reinstalled it via a google download just to see if I can get your issue and dig deeper. But sad to say: I can’t get the error. So I’m sorry to say that I can’t help this time.
If this is the long-standing key issue (not something new),
The key is associated with a signed library (subcomponent) of Chrome.
For various internal legal reasons, the key is required but for unknown reasons (maybe some more legal?) the “secret” isn’t embedded in the main app.
Ignoring and continueing is probably the easiest solution.
But, if you want to fix the problem so it doesn’t appear, I do remember there is a thread somewhere in this Forum’s archives where someone posted the key and how to install.
i have not chosen the ignore option since i dont really understand what is going on (and dont want to get hacked). The issue has also come up on mailing list so ill wait and go with the ignore/continue if all else fails.
well google compiled and signed that package but they didn’t include the public key in their own repository it’s a google issue but
a quick google search reveals this https://www.google.com/linuxrepositories/
according to that page you can import the google key using rpm command (you can use copy/paste)
after importing the public key that warning should be gone
personally I think Chromium is a better choice then Chrome for security reasons but I don’t use any of them
I didn’t read your first post entiraly :shame:
apparently you do have google’s key but the error persists
well that’s a google bug and you’re unsure of the validity of the rpm package (it was downloaded via https from a trusted source) you’re thinking it might be a mim attack
you have three choices report it to google or ignore it or use chromium as it’s build and signed by opensuse team there’s nothing they can do about 3rd party propitiatory code
It’s not a good idea to ignore since their repo could have been hacked.
Just to add a bit of info: having looked at threads from when this happened in the past, I erased my previously imported key (sudo rpm -e gpg-pubkey-7fac5991-*) and reimported the key. Alas, this made no difference.
If anyone finds a reliable place to download this key, please let us know.
I’m not a Chrome hater but I don’t get why not use Chromium as for some time now the pdf plugin is opensourced and included with Chromium, google stopped bundling flash (they don’t develop it anymore adobe does) and you have to get it from packman and you can get chromium-plugin-widevinecdm from packman so you can watch all your DRM’ed videos like netflix etc
so I don’t get it why get Chrome when you can get Chromium?
> so I don’t get it why get Chrome when you can get Chromium?
because the last time i tried chromium (9 months ago) there where minor frustrations - cant remember exactly, maybe flash/video playback etc.
Your saying there are no longer ANY advantages in using chrome?
but i do need to include chromium-plugin-widevinecdm, any other libs?
Because if you do some frontend web dev you would want to make sure that your pages work correctly in Chrome which most people use. Chromium and Chrome don’t seem to be absolutely identical in certain situations. I can’t recall a specific case but I have seen it happening.
As result of an earlier thread about this same issue, quite a while ago I uninstalled chrome and installed chromium. I did it because someone in the thread said “why not chromium”. Chromium gave me occasional video problems and occasional screen lock and once or twice even had to power-off / power-on reboot. I eventually plugged in an Nvidia card and that fixed the chromium problem.
That was a Dell machine. Now I have a Lenovo – and I’m back to Chrome which so far hasn’t missed a beat in Leap 42.2.
However my Leap 42.3 is having issues in Chrome but I put that down to 42.3 being so new.
you have reported a google-chrome problem to the chromium project? (i would have thought they where different esp. respect to repository/signing issues)
OK. Have just noticed there is an option in the menu->help->report an issue. Perhaps if everyone reports, our voice will be heard above the noise (or maybe not)