I just noticed that pidgin (well, more specifically, libpurple) is shipping its own certs. There is some overlap here as some root certs that we ship are duplicated between pidgin and ca-certifaces, and additionally, pidgin is shipping some certs that have been refused into NSS so far (such as CACert). Also, noticed that there is an option to build --with-system-ssl-certs that we aren't using. We should consolidate here if possible.
Unfortunately pidgin (libpurple) doesn't support multiple certificates in one file (ala ca-bundle.crt), so we can't use --with-system-ssl-certs (yet).
Oh, that kinda throws a damper on this doesn't it? :-) Is there an upstream bug to track that?
(In reply to comment #2) > Oh, that kinda throws a damper on this doesn't it? :-) Is there an upstream > bug to track that? No, not that I know of. But it has been on my personal TODO list for far too long, and your report was enough for me to do something about that. Assuming I didn't screw it up too bad, Pidgin 2.7.0 will support using Fedora style system CA certs (in a bundle). It required additional API, so can't be backported to 2.6.x without breaking upstream versioning rules.
pidgin-2.7.0-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/pidgin-2.7.0-1.fc12
pidgin-2.7.0-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/pidgin-2.7.0-1.fc13
pidgin-2.7.0-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/pidgin-2.7.0-1.fc11
pidgin-2.7.0-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update pidgin'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pidgin-2.7.0-1.fc13
pidgin-2.7.0-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update pidgin'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pidgin-2.7.0-1.fc11
pidgin-2.7.0-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update pidgin'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pidgin-2.7.0-1.fc12
pidgin-2.7.0-2.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update pidgin'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pidgin-2.7.0-2.fc12
pidgin-2.7.0-2.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update pidgin'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pidgin-2.7.0-2.fc13
pidgin-2.7.0-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update pidgin'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/pidgin-2.7.0-2.fc11
pidgin-2.7.0-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
pidgin-2.7.0-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
pidgin-2.7.0-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.