Merge pull request #6779 from MicrosoftDocs/rothja-patch-1

Removing setion mistakenly added to article

Author: PRMerger17

docs/linux/sql-server-linux-encrypted-connections.md

@@ -1,9 +1,9 @@
 ---
 title: Encrypting Connections to SQL Server on Linux | Microsoft Docs
 description: This article describes Encrypting Connections to SQL Server on Linux.
-author: tmullaney 
+author: vin-yu 
 ms.date: 01/30/2018
-ms.author: meetb 
+ms.author: vinsonyu 
 manager: craigg
 ms.topic: conceptual
 ms.prod: sql
@@ -28,11 +28,6 @@ Before getting started, you need to make sure your certificates follow these req
 - The certificate must be created by using the KeySpec option of AT_KEYEXCHANGE. Usually, the certificate's key usage property (KEY_USAGE) also includes key encipherment (CERT_KEY_ENCIPHERMENT_KEY_USAGE).
 - The Subject property of the certificate must indicate that the common name (CN) is the same as the host name or fully qualified domain name (FQDN) of the server computer. Note: Wild Card Certificates are supported.
 
-## Configuring the OpenSSL Libraries for Use (Optional)
-You can create symbolic links in the `/opt/mssql/lib/` directory that reference which `libcrypto.so` and `libssl.so` libraries should be used for encryption. This is useful if you want to force SQL Server to use a specific version of OpenSSL other than the default provided by the system. If these symbolic links are not present, SQL Server will load the default configured OpenSSL libraries on the system.
-
-These symbolic links should be named `libcrypto.so` and `libssl.so` and placed in the `/opt/mssql/lib/` directory.
-
 ## Overview
 TLS is used to encrypt connections from a client application to [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)]. When configured correctly, TLS provides both privacy and data integrity for communications between the client and the server.  TLS connections can either be client initiated or server initiated.