|
From: Tadashi M. <ta...@my...> - 2013-12-11 19:19:25
|
Hi, Mr. Braun, The problem is caused by the update of a SSL certificate for api.twitter.com. The update is described at https://dev.twitter.com/blog/rest-api-ssl-certificate-updates . There are two ways to avoid the problem. * Update twittering-mode.el. I have committed a patch to the repository on GitHub. It adds all CA certificates available on https://www.symantec.com/page.jsp?id=roots . The latest version will work without the problem. You can get it at https://github.com/hayamiz/twittering-mode/raw/master/twittering-mode.el or https://github.com/hayamiz/twittering-mode/raw/3.0.x/twittering-mode.el . * Suppress the error. If it is difficult to update twittering-mode.el, you can suppress the error by the following configuration. (setq twittering-allow-insecure-server-cert t) The configuration may weaken security because it disables server authentication. Please try it. # To follow the update, I had added a root CA certificate # `PCA-3G3.pem' to `twittering-mode.el' on GitHub at Dec 9. However, # The new SSL certificate for api.twitter.com requires `PCA-3G5.pem'... # Since twittering-mode.el now includes all root CA certificates on # the above site, I hope that such a problem will not happen. Regards, Tadashi MATSUO |