Replacing a broken link (#4560)

Hi.
The link that I replaced was broken; because mxr.mozilla.org doesn't exist anymore.
Here are some more general pages that lead to the link I added to this document:
https://wiki.mozilla.org/CA/Included_Certificates
https://wiki.mozilla.org/CA/FAQ
https://wiki.mozilla.org/CA/Included_CAs

Co-authored-by: Rich Trott <rtrott@gmail.com>

locale/en/knowledge/cryptography/how-to-use-the-tls-module.md

@@ -18,7 +18,7 @@ layout: knowledge-post.hbs
 
 In public-key cryptography, each peer has two keys: A public key, and a private key. The public key is shared with everyone, and the private key is (naturally) kept secret. In order to encrypt a message, a computer requires its private key and the recipient's public key. Then, in order to decrypt the message, the recipient requires its *own* private key and the *sender*'s public key.
 
-In TLS connections, the public key is called a *[certificate](https://en.wikipedia.org/wiki/Digital_certificate)*. This is because it's "[signed](https://en.wikipedia.org/wiki/Digital_signature)" to prove that the public key belongs to its owner. TLS certificates may either be signed by a third-party certificate authority (CA), or they may be [self-signed](https://en.wikipedia.org/wiki/Self-signed_certificate). In the case of Certificate Authorities, Mozilla keeps [a list of trusted root CAs](http://mxr.mozilla.org/mozilla/source/security/nss/lib/ckfw/builtins/certdata.txt) that are generally agreed upon by most web browsers. These root CAs may then issue certificates to other signing authorities, which in turn sign certificates for the general public.
+In TLS connections, the public key is called a *[certificate](https://en.wikipedia.org/wiki/Digital_certificate)*. This is because it's "[signed](https://en.wikipedia.org/wiki/Digital_signature)" to prove that the public key belongs to its owner. TLS certificates may either be signed by a third-party certificate authority (CA), or they may be [self-signed](https://en.wikipedia.org/wiki/Self-signed_certificate). In the case of Certificate Authorities, Mozilla keeps [a list of trusted root CAs](https://ccadb-public.secure.force.com/mozilla/CAInformationReport) that are generally agreed upon by most web browsers. These root CAs may then issue certificates to other signing authorities, which in turn sign certificates for the general public.
 
 ### History of TLS/SSL Support in Node.js