Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10597 - pidgin-2.4.2 provides its own CA certificates.

Attached to Project: Arch Linux
Opened by Eric Belanger (Snowman) - Friday, 06 June 2008, 17:58 GMT
Last edited by Alexander Fehr (pizzapunk) - Tuesday, 26 August 2008, 10:20 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Alexander Fehr (pizzapunk)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I just noticed that pidgin provides its own CA certificates in /usr/share/purple/ca-certs. It might be a good idea to use the ones provided by the new ca-certificates package instead.

BTW, I don't use neither pidgin nor these certificates so I can't say if the pidgin's feature that uses them will still work with the certificates provided by ca-certificates. This FR is just to let you know about this situation.
This task depends upon

Closed by  Alexander Fehr (pizzapunk)
Tuesday, 26 August 2008, 10:20 GMT
Reason for closing:  Fixed
Additional comments about closing:  pidgin 2.5.0-2
Comment by Dan McGee (toofishes) - Saturday, 07 June 2008, 00:13 GMT
I think I got this working locally (required a patch), and even opened/fixed a pidgin bug (http://developer.pidgin.im/ticket/6036) in the process. I'll test for a few days locally and then push this out.
Comment by Dan McGee (toofishes) - Tuesday, 17 June 2008, 22:14 GMT
Please don't close my bugs unless you make a note first on something like this...this is fixed upstream in a *future* version but I want to remember to make the changes necessary when 2.5.0 comes out.
Comment by Dan McGee (toofishes) - Thursday, 10 July 2008, 12:00 GMT
A note for pidgin and the upcoming 2.5.0 release- they added a new
configure option that replaces our need to patch for the certificate
location, so the patch can be removed with that release and the
following change made to the PKGBUILD (in addition to all the patch
removal):
@@ -38,6 +34,7 @@
automake --add-missing || return 1

./configure --prefix=/usr --sysconfdir=/etc \
+ --with-ssl-certificates=/etc/ssl/certs
--disable-perl --disable-cap \
--disable-schemas-install \
--enable-gtkspell --enable-gnutls=yes \

Loading...