You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mina.apache.org by el...@apache.org on 2016/02/11 09:58:15 UTC

svn commit: r1729780 - /mina/site/trunk/content/mina-project/userguide/ch11-ssl-filter/ch11-ssl-filter.mdtext

Author: elecharny
Date: Thu Feb 11 08:58:15 2016
New Revision: 1729780

URL: http://svn.apache.org/viewvc?rev=1729780&view=rev
Log:
centering the images

Modified:
    mina/site/trunk/content/mina-project/userguide/ch11-ssl-filter/ch11-ssl-filter.mdtext

Modified: mina/site/trunk/content/mina-project/userguide/ch11-ssl-filter/ch11-ssl-filter.mdtext
URL: http://svn.apache.org/viewvc/mina/site/trunk/content/mina-project/userguide/ch11-ssl-filter/ch11-ssl-filter.mdtext?rev=1729780&r1=1729779&r2=1729780&view=diff
==============================================================================
--- mina/site/trunk/content/mina-project/userguide/ch11-ssl-filter/ch11-ssl-filter.mdtext (original)
+++ mina/site/trunk/content/mina-project/userguide/ch11-ssl-filter/ch11-ssl-filter.mdtext Thu Feb 11 08:58:15 2016
@@ -78,7 +78,9 @@ As it's a protocol, it requires some dia
 
 It's enough to know that any secured exchange is precluded by a negociation phase, called the **Handshake**, which role is to come to an agreement between the client and the server on what will be the encryption method to use. A basic **SSL/TLS** session will be something that looks like :
 
+<DIV align="center">
 ![TLS Protocol](../images/TLS-protocol.png)
+</DIV>
 
 As you can see in this picture, it's a 2 phases protocol : first the handshake, then when completed the client and the server will be able to exchange data that will be encrypted.
 
@@ -114,10 +116,14 @@ One important thing is that you may writ
 
 All in all, the **SSL/TLS** processing is like a black box that accept only one input and can't process anything until it has completed its task. the following schema represent the way it works for outgoing messages.
 
+<DIV align="center">
 ![Outgoing messages](../images/TLS-outMessage.png)
+</DIV>
 
 It's not that different for incoming messages, except that we won't have an **Executor** between the **IoProcessor** and the **SslFilter**. That makes things simpler, except that one critical thing happens : when we process an incoming message, we can't anymore process outgoiing messages. Note that it also works on the other way around : when an outgoing message is being processed, we can't process an incomoing message :
 
+<DIV align="center">
 ![Incoming message](../images/TLS-inMessage.png)
+</DIV>