Bug 470697

Summary: "Trust certificate forever" doesn't work
Product: [Applications] akregator Reporter: Bill Dietrich <kdebt4>
Component: generalAssignee: kdepim bugs <pim-bugs-null>
Status: REPORTED ---    
Severity: normal    
Priority: NOR    
Version First Reported In: 5.23.1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Bill Dietrich 2023-06-06 10:03:39 UTC 
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
Comment 1 Bill Dietrich 2023-06-06 10:05:52 UTC 
A site where this happens (currently) is https://trugman-internals.com/
Comment 2 Bill Dietrich 2025-09-28 08:46:04 UTC 
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 ?
Comment 3 Bill Dietrich 2025-10-01 21:31:57 UTC 
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.
Comment 4 Bill Dietrich 2025-10-06 08:50:07 UTC 
Okay, it just happened again, rule created ends with

    qorg11.net=ExpireUTC 3025-10-06T09:34:01,HostNameMismatch,SelfSignedCertificate

I get the "failed" dialog, click Details, get next dialog, click Forever.  But it happens again later.  Now I have two rules for same site.  "Forever" is not working.