Changes between Version 12 and Version 13 of MSNCertIssue

Timestamp:

Jan 22, 2013, 12:14:05 AM (11 years ago)

Author:

MarkDoliner

Comment:

Link to root cert using https to reduce the likelihood of man-in-the-middle

MSNCertIssue

@@ -2 +2 @@
 MSN recently changed the certificate used on some of their servers.  This certificate is used to negotiate a secure socket layer (SSL) session, an encrypted connection, between the client (Windows Live Messenger, Pidgin, etc.) and the server(s).
 
-Unfortunately, this new certificate is signed by a root certificate that Pidgin does not provide. You may not see this problem if your distribution provides the root certificate and has configured Pidgin to use it. The error message you'll see is something like this:
+Unfortunately, this new certificate is signed by a root certificate that Pidgin does not provide. You may not experience any problems if your distribution provides the root certificate and has configured Pidgin to use it. If you do experience a problem, you'll see one of these error messages:
 
 '''Unable to validate certificate:'''[[BR]]
@@ -36 +36 @@
 ''If you have followed other (incorrect) instructions to replace the 'local-bay.contacts.msn.com' or 'local-blu-people.directory.live.com' certificate, then you must delete that certificate from `Tools->Certificates` first.''
 
-Download [http://hg.pidgin.im/pidgin/main/raw-file/default/share/ca-certs/Baltimore_CyberTrust_Root.pem Baltimore_CyberTrust_Root.pem], then follow the appropriate set of directions below.
+Download [https://hg.pidgin.im/pidgin/main/raw-file/default/share/ca-certs/Baltimore_CyberTrust_Root.pem Baltimore_CyberTrust_Root.pem], then follow the appropriate set of directions below.
 
 === Windows ===