Some time in the past month-ish pidgin started repeatedly prompting to accept a TLS certificate on every connection attempt, including when it re-establishes connection after transient network outage. "Accept certificate for irc.libera.chat? The certificate for irc.libera.chat could not be validated. The certificate is not trusted because no certificate that can verify it is currently trusted." The issue seems to affect my connections to OFTC and Libera IRC networks. I found a recent upstream bug report which is suggesting a regression has been caused by an NSS update https://issues.imfreedom.org/issue/PIDGIN-17886/Certificate-verification-errors-with-NSS-3.103 which has an upstream fix https://keep.imfreedom.org/pidgin/pidgin/rev/412b2a4de898/ I've not tested if this fixes my problem, but it looks close enough to be plausible since pidgin in Fedora is built with NSS, and the update to 3.103 NSS arrived in Fedora in the time window where I first saw this regression. Could you look at getting this pidgin (libpurple) fix into Fedora packages. Note, I'm using the latest Fedora flatpak of pidgin, reported as being: Pidgin 2.14.13-2.fc41app1 (libpurple 2.14.13) 1392ea316bd054f5f3d29b6954198d8b9e4f27fb Reproducible: Always Steps to Reproduce: 1. Connect to irc.libera.chat with TLS 2. 3. Actual Results: "SSL Certification Verification" popup appears every time. Expected Results: No certificate verification popups on connect
IMHO it's already in F41, but I don't know whether it fixes the problem. pidgin-2.14.13-4.fc41: * Tue Nov 5 2024 Jaroslav Škarvada <jskarvad> - 2.14.13-4 - Fixed nss get peer certificate Resolves: rhbz#2311054
(In reply to Jaroslav Škarvada from comment #1) > IMHO it's already in F41, but I don't know whether it fixes the problem. > pidgin-2.14.13-4.fc41: > * Tue Nov 5 2024 Jaroslav Škarvada <jskarvad> - 2.14.13-4 > - Fixed nss get peer certificate > Resolves: rhbz#2311054 Well, it's in the updates-testing now, but it should get into stable soon.
There was a problem in the spec and the patch wasn't applied, fixed in 2.14.13-5. *** This bug has been marked as a duplicate of bug 2311054 ***