Spurious SSL certificate error when Gajim can't find pyasn1
Duck Duck Go, the privacy-focused search engine company, runs an XMPP service at dukgo.com:
When connecting, Gajim shows the following error message:
"Error verifying SSL certificate There was an error verifying the SSL certificate of your jabber server: The authenticity of the dukgo.com certificate could be invalid. The certificate does not cover this domain."
Other IM clients (including Pidgin) work just fine with this server, so Gajim is obviously missing something. Perhaps it's failing to look at the certificate's Subject Alt Name?
I was unable to work around the problem by putting the certificate's Common Name (duck.co) into Gajim's Connect Server advanced config. This suggests that Gajim is checking the Common Name against something other than the server name it used to connect. If that is the case, it would be a second bug.