A FIX: pidgin/AIM 'certificate chain invalid' error redux

[oj]

The pidgin "api.screenname.aol.com could not be validated" error has a long history. (there are other AOL urls but same error) Is anyone seeing this happen now with pidgin using AOL/ AIM? I just had all my accounts tossed by this error across several platforms, all running Mageia 5 and the latest updates. One computer 'A' had account 'A' thrown off a few days ago. My own computer 'B' and AIM account 'B' just got thrown to the dogs a moment ago. I find no results in searches for any combo of terms in the error messages I am receiving. Using kopete works fine. It's obviously a pidgin specific problem. I'd rather never use IM than use kopete. The latter is worse than a sharp stick in the eye, IMO.

Anyone else having pidgin/AIM problems starting about 2 days ago? As I said I get no results in any searches here with AIM, pidgin, and any number of very specific error texts.

[jiml8]

Pidgin first crapped a few weeks ago on my Yahoo IM account, but apparently Yahoo made an abrupt change. Pidgin then started rejecting certificates from my Google Hangouts account, which I need for work.

So I have stopped running pidgin.

[oj]

Finally had some time to chase around, and in another seemingly non-related post there was a link to this:

http://lists.opensuse.org/opensuse-bugs/2013-07/msg03608.html

I did the recommended chmod (as root):

Code: Select all

chmod 000 /usr/lib64/purple-2/ssl-gnutls.so

...and pidgin started fine and logged in normally.

Read the bug report for why this works, if interested. I just hope this doesn't break something else.

[jiml8]

Well, by golly gum! That worked.

I guess there must be an error in that library.