SUMMARY *** If a site's certificate is "self-signed and untrusted", "trust forever" doesn't work. *** STEPS TO REPRODUCE 1. Fetch feed. 2. Get "bad cert" error. 3. Click "continue". 4. Somewhere in here is "details" button, clicking it shows cert is "self-signed and untrusted". 5. Get dialog offering to trust forever or for this session. 6. Click on "forever" button. 7. Next time you launch Akregator, same exact thing will happen, cert is not "trusted forever". SOFTWARE/OS VERSIONS Linux/KDE Plasma: Flatpak (available in About System) KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9
A site where this happens (currently) is https://trugman-internals.com/
Still happens on Akregator Version 6.3.3 (24.12.3) natively installed on Kubuntu 25.04. Using ChatGPT to investigate the code, I wonder if Akregator has been compiled with the flag WITH_QTDBUS defined ? If that flag is not defined, the rule for the certificate won't be stored. Maybe Help/About should report the status of that flag. Or is there another way to find out, at run-time ?
I see rules being stored in ~/.config/ksslcertificatemanager so WITH_QTDBUS is not the problem. I think I no longer have any site with a bad cert in the particular way this was happening, so I'm no longer sure it still IS happening.