Recently received a warning about an unknown signing key when refreshing a repository via YaST2, and was asked if I wanted to continue. I thought selecting “Yes” and checking “Do not show this warning again” would resolve the problem, but now I regret that course of action. Any idea how I can configure YaST2 to show those warnings again? (I’m on Tumbleweed, mostly up to date.)
Thanks – please let me know if I’ve left out anything important.
I’m not sure, but I will guess:
First become root in a terminal.
cd /root/.config
rm -rf YaST2
That should clear Yast settings.
That seems like a reasonable course of action, although I don’t see any mention of ignoring keys or warnings in the included files. Perhaps it was a session-only kind of thing, rather than global?
I’m not sure whether it will solve your specific problems.
Some settings come from zypp “/etc/zypp/*.conf”, but I don’t think those are set automatically. Some settings might be in the RPM database. I’m not sure how you change those. And perhaps that’s where the key warnings go.
I think this setting apply to the specific repo, not to all. So perhaps removing and adding (maybe with a repo refresh in between) the repo will bring the message back?
Just guessing, mind you.
I haven’t yet deleted any of the referenced configuration files, but I have now deleted and recreated the repo, so I’ll check back in if I manage to regenerate the warning/error message.
For background, I put myself in this situation while trying to diagnose what is apparently an issue with zypper’s inability to handle subkeys, and Google’s recent switch to signing chrome with a subkey; also there seems to be an issue with the post-installation script no longer creating a Google repository entry under Tumbleweed. See below for some reference:
https://bugzilla.opensuse.org/show_bug.cgi?id=1008325
https://bugs.chromium.org/p/chromium/issues/detail?id=750481
https://forums.opensuse.org/showthread.php/526290-Google-Chrome-Update-Key-Validation-Error/page2
In the course of stumbling around this issue, I’ve re-imported their public key, which may or may not have resolved the missing key issue, so I might not be able to generate the original warning anymore. I’ve also manually recreated the repo. Nonetheless, the Software Update applet still seems to choke on lack of trust. I seem to be able to update from within zypper now, though. Go figure.
Forgot to mention, thanks for the help.