DOCS-4295 DOCS-5272 include TLS when mentioning SSL

Author: kay-kim

source/administration/install-on-linux.txt

@@ -12,7 +12,7 @@ Recommended
 
 For the best installation experience, MongoDB provides packages for popular
 Linux distributions. These packages, which support
-specific platforms and provide improved performance and SSL
+specific platforms and provide improved performance and TLS/SSL
 support, are the preferred way to run MongoDB. The following guides
 detail the installation process for these systems:
 
@@ -25,7 +25,7 @@ Manual Installation
 -------------------
 
 For Linux systems without supported packages, MongoDB provides a
-generic Linux release. These versions of MongoDB don't include SSL,
+generic Linux release. These versions of MongoDB don't include TLS/SSL,
 and may not perform as well as the targeted packages, but are
 compatible on most contemporary Linux systems. See the
 following guides for installation:

source/administration/production-notes.txt

@@ -492,8 +492,8 @@ For all MongoDB deployments:
 - Use the Network Time Protocol (NTP) to synchronize time among
   your hosts. This is especially important in sharded clusters.
 
-MongoDB and SSL Libraries
-`````````````````````````
+MongoDB and TLS/SSL Libraries
+`````````````````````````````
 
 On Linux platforms, you may observe one of the following statements in
 the MongoDB log:
@@ -503,8 +503,8 @@ the MongoDB log:
    <path to SSL libs>/libssl.so.<version>: no version information available (required by /usr/bin/mongod)
    <path to SSL libs>/libcrypto.so.<version>: no version information available (required by /usr/bin/mongod)
 
-These warnings indicate that the system's SSL libraries are different
-from the SSL libraries that the :program:`mongod` was compiled against.
+These warnings indicate that the system's TLS/SSL libraries are different
+from the TLS/SSL libraries that the :program:`mongod` was compiled against.
 Typically these messages do not require intervention; however, you can
 use the following operations to determine the symbol versions that
 :program:`mongod` expects:
@@ -528,8 +528,8 @@ operations to detect symbol version mismatches:
 
 .. code-block:: sh
 
-   objdump -T <path to SSL libs>/libssl.so.1*
-   objdump -T <path to SSL libs>/libcrypto.so.1*
+   objdump -T <path to TLS/SSL libs>/libssl.so.1*
+   objdump -T <path to TLS/SSL libs>/libcrypto.so.1*
 
 This procedure is neither exact nor exhaustive: many symbols used by
 :program:`mongod` from the ``libcrypto`` library do not begin with

source/administration/security-checklist.txt

@@ -38,10 +38,10 @@ See :doc:`/core/authorization`, :doc:`/tutorial/define-roles`,
 Encrypt Communication
 ---------------------
 
-Configure MongoDB to use SSL for all incoming and outgoing
-connections. Use SSL to encrypt communication between
+Configure MongoDB to use TLS/SSL for all incoming and outgoing
+connections. Use TLS/SSL to encrypt communication between
 :program:`mongod` and :program:`mongos` components of a MongoDB
-client, as well as between all applications and MongoDB.
+client as well as between all applications and MongoDB.
 
 See :doc:`/tutorial/configure-ssl`.
 

source/core/authentication.txt

@@ -181,7 +181,7 @@ x.509 Certificate Authentication
 .. versionadded:: 2.6
 
 MongoDB supports x.509 certificate authentication for use with a secure
-:doc:`SSL connection </tutorial/configure-ssl>`.
+:doc:`TLS/SSL connection </tutorial/configure-ssl>`.
 
 To authenticate to servers, clients can use x.509 certificates instead
 of usernames and passwords. See :ref:`x509-client-authentication` for

source/core/replica-set-arbiter.txt

@@ -59,7 +59,7 @@ The only communication between arbiters and other set members are:
 votes during elections, heartbeats, and configuration data. These
 exchanges are not encrypted.
 
-**However**, if your MongoDB deployment uses SSL, MongoDB will encrypt
+**However**, if your MongoDB deployment uses TLS/SSL, MongoDB will encrypt
 *all* communication between replica set members. See
 :doc:`/tutorial/configure-ssl` for more information.
 

source/core/security-introduction.txt

@@ -76,9 +76,9 @@ Encryption
 Transport Encryption
 ~~~~~~~~~~~~~~~~~~~~
 
-You can use SSL to encrypt all of MongoDB's network traffic. SSL
-ensures that MongoDB network traffic is only readable by the intended
-client.
+You can use TLS/SSL (Transport Layer Security/Secure Sockets Layer) to
+encrypt all of MongoDB's network traffic. TLS/SSL ensures that MongoDB
+network traffic is only readable by the intended client.
 
 See :doc:`/tutorial/configure-ssl` for more information.
 

source/core/security-network.txt

@@ -140,7 +140,7 @@ Virtual Private Networks
 
 Virtual private networks, or VPNs, make it possible to link two
 networks over an encrypted and limited-access trusted
-network. Typically MongoDB users who use VPNs use SSL rather than
+network. Typically, MongoDB users who use VPNs use TLS/SSL rather than
 IPSEC VPNs for performance issues.
 
 Depending on configuration and implementation, VPNs provide for

source/faq/replica-sets.txt

@@ -206,9 +206,9 @@ following data with the rest of the replica set:
 - Replica set configuration data and voting data. This information is
   not encrypted. Only credential exchanges are encrypted.
 
-If your MongoDB deployment uses SSL, then all communications between
-arbiters and the other members of the replica set are secure. See the
-documentation for :doc:`/tutorial/configure-ssl` for more
+If your MongoDB deployment uses TLS/SSL, then all communications
+between arbiters and the other members of the replica set are secure.
+See the documentation for :doc:`/tutorial/configure-ssl` for more
 information. Run all arbiters on secure networks, as with all MongoDB
 components.
 

source/includes/admonition-saslauthd-ldap-considerations.rst

@@ -8,4 +8,4 @@ Use secure encrypted or trusted connections between clients and the server,
 as well as between ``saslauthd`` and the LDAP server. The LDAP server uses
 the ``SASL PLAIN`` mechanism, sending and receiving data in **plain text**. 
 You should use only a trusted channel such as a VPN, a connection encrypted 
-with SSL, or a trusted wired network.
+with TLS/SSL, or a trusted wired network.

source/includes/extracts-security-prereq.yaml

@@ -3,52 +3,52 @@ inherit:
   ref: _security-prereq
   file: extracts-security-prereq-base.yaml
 replacement: 
-  unscoped: "A full description of SSL, PKI (Public Key Infrastructure) certificates, and Certificate Authority"
+  unscoped: "A full description of TLS/SSL, PKI (Public Key Infrastructure) certificates, and Certificate Authority"
   page: page
-  prereq: "SSL as well as access to valid certificates"
+  prereq: "TLS/SSL as well as access to valid certificates"
 ---
 ref: security-prereq-configure-ssl-clients
 inherit:
   ref: _security-prereq
   file: extracts-security-prereq-base.yaml
 replacement:
-  unscoped: "A full description of SSL, PKI (Public Key Infrastructure) certificates, and Certificate Authority"
+  unscoped: "A full description of TLS/SSL, PKI (Public Key Infrastructure) certificates, and Certificate Authority"
   page: page
-  prereq: "SSL as well as access to valid certificates"
+  prereq: "TLS/SSL as well as access to valid certificates"
 ---
 ref: security-prereq-upgrade-cluster-to-ssl
 inherit:
   ref: _security-prereq
   file: extracts-security-prereq-base.yaml
 replacement:
-  unscoped: "A full description of SSL, PKI (Public Key Infrastructure) certificates, and Certificate Authority"
+  unscoped: "A full description of TLS/SSL, PKI (Public Key Infrastructure) certificates, and Certificate Authority"
   page: tutorial
-  prereq: "SSL as well as access to valid certificates"
+  prereq: "TLS/SSL as well as access to valid certificates"
 ---
 ref: security-prereq-configure-fips
 inherit:
   ref: _security-prereq
   file: extracts-security-prereq-base.yaml
 replacement:
-  unscoped: "A full description of FIPS and SSL"
+  unscoped: "A full description of FIPS and TLS/SSL"
   page: tutorial
-  prereq: "FIPS and SSL"
+  prereq: "FIPS and TLS/SSL"
 ---
 ref: security-prereq-configure-x509-client-authentication
 inherit:
   ref: _security-prereq
   file: extracts-security-prereq-base.yaml
 replacement:
-  unscoped: "A full description of SSL, PKI (Public Key Infrastructure) certificates, in particular x.509 certificates, and Certificate Authority"
+  unscoped: "A full description of TLS/SSL, PKI (Public Key Infrastructure) certificates, in particular x.509 certificates, and Certificate Authority"
   page: tutorial
-  prereq: "SSL as well as access to valid x.509 certificates"
+  prereq: "TLS/SSL as well as access to valid x.509 certificates"
 ---
 ref: security-prereq-configure-x509-member-authentication
 inherit:
   ref: _security-prereq
   file: extracts-security-prereq-base.yaml
 replacement:
-  unscoped: "A full description of SSL, PKI (Public Key Infrastructure) certificates, in particular x.509 certificates, and Certificate Authority"
+  unscoped: "A full description of TLS/SSL, PKI (Public Key Infrastructure) certificates, in particular x.509 certificates, and Certificate Authority"
   page: tutorial
-  prereq: "SSL as well as access to valid x.509 certificates"
+  prereq: "TLS/SSL as well as access to valid x.509 certificates"
 ...