Bug 2311054 - Repeating certificate accept dialog (nss-3.103)
Summary: Repeating certificate accept dialog (nss-3.103)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 39
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2325435 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-10 09:11 UTC by Pavol Šimo
Modified: 2025-03-22 04:25 UTC (History)
7 users (show)

Fixed In Version: pidgin-2.14.13-4.fc42 pidgin-2.14.13-5.fc42 pidgin-2.14.13-4.fc40 pidgin-2.14.13-5.fc41
Clone Of:
Environment:
Last Closed: 2024-11-05 13:17:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pavol Šimo 2024-09-10 09:11:34 UTC
Pidgin repeatedly displays dialog to accept certificate.
It is caused by change in nss library in version 3.103

Patch exists, please add from https://issues.imfreedom.org/issue/PIDGIN-17886/Certificate-verification-errors-with-NSS-3.103
Functionality of the patch is verified (https://github.com/EionRobb/purple-teams/issues/60)

Reproducible: Always

Comment 1 Brian J. Murrell 2024-10-25 15:07:59 UTC
The above mentioned patch has now landed in the release track for pidgin:
https://keep.imfreedom.org/pidgin/pidgin/rev/412b2a4de898/

Could we please get a release made with this patch added.

It is worth noting that pidgin 2.14.13 is also now available where Fedora 40 currently only has 2.14.12, so it is one bug-fix release behind.  It would seem that bug 2265633 simply needs backporting to currently supported Fedora releases.

It would be nice to get both updates in a new package soon please as this recurring dialog is very annoying and it happens many times per day.

Comment 2 Fedora Update System 2024-11-05 13:14:43 UTC
FEDORA-2024-fa6839da46 (pidgin-2.14.13-4.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-fa6839da46

Comment 3 Fedora Update System 2024-11-05 13:17:41 UTC
FEDORA-2024-fa6839da46 (pidgin-2.14.13-4.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Jaroslav Škarvada 2024-11-05 13:27:00 UTC
I would fix it in f40, not in f39, becase it's nearly EOL.

Comment 5 Fedora Update System 2024-11-05 14:04:18 UTC
FEDORA-2024-76cb7f9a19 (pidgin-2.14.13-4.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-76cb7f9a19

Comment 6 Fedora Update System 2024-11-05 14:15:17 UTC
FEDORA-2024-520eba27ca (pidgin-2.14.13-4.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-520eba27ca

Comment 7 Fedora Update System 2024-11-06 05:11:33 UTC
FEDORA-2024-520eba27ca has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-520eba27ca`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-520eba27ca

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2024-11-06 07:01:48 UTC
FEDORA-2024-76cb7f9a19 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-76cb7f9a19`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-76cb7f9a19

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Zdenek Dohnal 2024-11-07 09:31:58 UTC
Hi all,

the update looked ok at first in F40, but now pidgin asks for accepting cert with every startup and network change again.

I connect to libera.chat IRC server.

In the past I thought it was due change in crypto-policy - it looked libera was using SHA1 for fingerprint, so crypto library denied to work with SHA1 - but then I saw this bug.

Do you connect to a different IRC server or you don't use default crypto policy to have the patch working?

Comment 10 Jaroslav Škarvada 2024-11-12 14:54:45 UTC
*** Bug 2325435 has been marked as a duplicate of this bug. ***

Comment 11 Fedora Update System 2024-11-12 18:24:20 UTC
FEDORA-2024-793a0036f5 (pidgin-2.14.13-5.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-793a0036f5

Comment 12 Fedora Update System 2024-11-12 18:29:26 UTC
FEDORA-2024-793a0036f5 (pidgin-2.14.13-5.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2024-11-12 18:46:03 UTC
FEDORA-2024-ea8b3fdee7 (pidgin-2.14.13-5.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-ea8b3fdee7

Comment 14 Fedora Update System 2024-11-13 20:40:57 UTC
FEDORA-2024-ea8b3fdee7 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ea8b3fdee7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ea8b3fdee7

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2024-11-14 01:16:36 UTC
FEDORA-2024-520eba27ca (pidgin-2.14.13-4.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2024-11-21 03:35:29 UTC
FEDORA-2024-ea8b3fdee7 (pidgin-2.14.13-5.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 17 Red Hat Bugzilla 2025-03-22 04:25:32 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.