You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by sm...@apache.org on 2017/01/25 12:57:44 UTC

svn commit: r1780185 - /directory/site/trunk/content/api/user-guide/5.2-start-tls.mdtext

Author: smckinney
Date: Wed Jan 25 12:57:44 2017
New Revision: 1780185

URL: http://svn.apache.org/viewvc?rev=1780185&view=rev
Log:
nit

Modified:
    directory/site/trunk/content/api/user-guide/5.2-start-tls.mdtext

Modified: directory/site/trunk/content/api/user-guide/5.2-start-tls.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/5.2-start-tls.mdtext?rev=1780185&r1=1780184&r2=1780185&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/5.2-start-tls.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/5.2-start-tls.mdtext Wed Jan 25 12:57:44 2017
@@ -24,7 +24,7 @@ Notice: Licensed to the Apache Software
 
 # 5.2 - StartTLS
 
-As we have seen in the previous chapter, **LDAPS** has some drawbacks. There is a better alternative when it comes to securing communication -- using **startTLS**.
+As we have seen in the previous chapter, **LDAPS** has some drawbacks. There is a better alternative for securing communications between the client and server -- **startTLS**.
 
 The idea is to use an existing connection to send a message to the server and request it to be encrypted. We keep going with the current connection, on the same port, but the exchanged data will continue as encrypted.