matrix-tan.tar.gz_matrixssl_加密解密_系统/网络安全下载-pudn.com

<html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta charset="utf-8"> <meta name="generator" content="pdf2htmlEX"> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> <link rel="stylesheet" href="https://static.pudn.com/base/css/base.min.css"> <link rel="stylesheet" href="https://static.pudn.com/base/css/fancy.min.css"> <link rel="stylesheet" href="https://static.pudn.com/prod/directory_preview_static/622b8aa215da9b288bef99b7/raw.css"> <script src="https://static.pudn.com/base/js/compatibility.min.js"></script> <script src="https://static.pudn.com/base/js/pdf2htmlEX.min.js"></script> <script> try{ pdf2htmlEX.defaultViewer = new pdf2htmlEX.Viewer({}); }catch(e){} </script> <title></title> </head> <body> <div id="sidebar" style="display: none"> <div id="outline"> </div> </div> <div id="pf1" class="pf w0 h0" data-page-no="1"><div class="pc pc1 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/622b8aa215da9b288bef99b7/bg1.jpg"><div class="t m0 x1 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">Developer's Guide MatrixSSL 1.8 </div><div class="t m0 x1 h2 y2 ff1 fs0 fc0 sc0 ls2 ws2">Page 1 of 17 Copyright ©2002-2006 PeerSec Networks, Inc. </div><div class="t m0 x1 h3 y3 ff3 fs2 fc0 sc0 ls3 ws3">MatrixSSL Developer’s Guide </div><div class="t m0 x1 h2 y4 ff2 fs1 fc0 sc0 ls1 ws4">This document discusses developing with MatrixSSL. It includes instructions on </div><div class="t m0 x1 h2 y5 ff2 fs1 fc0 sc0 ls4 ws5">integrating MatrixSSL into an application and a description of the configurable options </div><div class="t m0 x1 h2 y6 ff2 fs1 fc0 sc0 ls5 ws6">for modifying the MatrixSSL library itself. </div><div class="t m0 x1 h2 y7 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h2 y8 ff2 fs1 fc0 sc0 ls6 ws7">Table of Contents </div><div class="t m0 x1 h2 y9 ff2 fs1 fc0 sc0 ls7 ws1">MatrixSSL Developer’s Guide ........................................................................................1 </div><div class="t m0 x2 h2 ya ff2 fs1 fc0 sc0 ls7 ws8">Commercial Version....................................................................................................1 </div><div class="t m0 x2 h2 yb ff2 fs1 fc0 sc0 ls7 ws8">Generating a Certificate Hierarchy...............................................................................2 </div><div class="t m0 x2 h2 yc ff2 fs1 fc0 sc0 ls7 ws8">Integrating with Applications.......................................................................................2 </div><div class="t m0 x2 h2 yd ff2 fs1 fc0 sc0 ls7 ws1">Re-handshaking...........................................................................................................6 </div><div class="t m0 x2 h2 ye ff2 fs1 fc0 sc0 ls7 ws8">Porting to Other Platforms...........................................................................................9 </div><div class="t m0 x3 h2 yf ff2 fs1 fc0 sc0 ls7 ws1">OS Dependent Code Layer ......................................................................................9 </div><div class="t m0 x3 h2 y10 ff2 fs1 fc0 sc0 ls7 ws8">Build Environment Details.......................................................................................9 </div><div class="t m0 x3 h2 y11 ff2 fs1 fc0 sc0 ls7 ws1">Windows Builds ......................................................................................................9 </div><div class="t m0 x3 h2 y12 ff2 fs1 fc0 sc0 ls7 ws1">Linux Builds............................................................................................................9 </div><div class="t m0 x3 h2 y13 ff2 fs1 fc0 sc0 ls7 ws1">MacOS X Builds....................................................................................................10 </div><div class="t m0 x3 h2 y14 ff2 fs1 fc0 sc0 ls7 ws8">VxWorks Builds....................................................................................................10 </div><div class="t m0 x3 h2 y15 ff2 fs1 fc0 sc0 ls7 ws1">Windows CE / PocketPC Builds ............................................................................11 </div><div class="t m0 x2 h2 y16 ff2 fs1 fc0 sc0 ls7 ws1">Extending MatrixSSL................................................................................................11 </div><div class="t m0 x3 h2 y17 ff2 fs1 fc0 sc0 ls7 ws8">Compile-Time Defines ..........................................................................................11 </div><div class="t m0 x3 h2 y18 ff2 fs1 fc0 sc0 ls7 ws9">Cipher Suites .........................................................................................................14 </div><div class="t m0 x3 h2 y19 ff2 fs1 fc0 sc0 ls7 ws1">Crypto Providers....................................................................................................16 </div><div class="t m0 x2 h2 y1a ff2 fs1 fc0 sc0 ls7 ws1">Debugging.................................................................................................................17 </div><div class="t m0 x1 h2 y1b ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h2 y1c ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h4 y1d ff4 fs3 fc0 sc0 ls8 wsa">Commercial Version </div><div class="t m0 x1 h2 y1e ff2 fs1 fc0 sc0 ls9 wsb">Some functions or features described in this document are available only in the </div><div class="t m0 x1 h2 y1f ff2 fs1 fc0 sc0 lsa wsc">commercially licensed version of MatrixSSL. Sections of this document that refer to the </div><div class="t m0 x1 h2 y20 ff2 fs1 fc0 sc0 lsb wsd">commercial version will be noted. </div><div class="t m0 x1 h2 y21 ff2 fs1 fc0 sc0 ls1 ws1"> </div></div><div class="pi" data-data='{"ctm":[1.568627,0.000000,0.000000,1.568627,0.000000,0.000000]}'></div></div> </body> </html>

<div id="pf2" class="pf w0 h0" data-page-no="2"><div class="pc pc2 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/622b8aa215da9b288bef99b7/bg2.jpg"><div class="t m0 x1 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">Developer's Guide MatrixSSL 1.8 </div><div class="t m0 x1 h2 y2 ff1 fs0 fc0 sc0 ls2 ws2">Page 2 of 17 Copyright ©2002-2006 PeerSec Networks, Inc. </div><div class="t m0 x1 h4 y22 ff4 fs3 fc0 sc0 lsc wse">Generating a Certificate Hierarchy </div><div class="t m0 x1 h2 y23 ff2 fs1 fc0 sc0 lsd wsf">The entire basis of strong security using SSL is the creation and maintenance of </div><div class="t m0 x1 h2 y24 ff2 fs1 fc0 sc0 lse ws10">certificate files. The standard security scenario for SSL is server authentication. That is, </div><div class="t m0 x1 h2 y25 ff2 fs1 fc0 sc0 lsf ws11">the client wants to make sure it is communicating with the correct server before sending </div><div class="t m0 x1 h2 y26 ff2 fs1 fc0 sc0 lsf ws11">any sensitive data. From a certificate file view, this is where the files should be located. </div><div class="t m0 x1 h2 y27 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x4 h5 y28 ff5 fs1 fc0 sc0 ls10 ws12">Server Client </div><div class="t m0 x5 h2 y29 ff2 fs1 fc0 sc0 ls11 ws13">serverCertificate.pem CAcertificate.pem </div><div class="t m0 x5 h2 y2a ff2 fs1 fc0 sc0 ls12 ws14">serverCertPrivateKey.pem </div><div class="t m0 x1 h2 y2b ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h2 y2c ff2 fs1 fc0 sc0 ls13 ws15">For information on how to create Certificate Authority root and child certificates please </div><div class="t m0 x1 h2 y2d ff2 fs1 fc0 sc0 ls14 ws16">see the MatrixSsl Key Generation</div><div class="t m0 x6 h2 y2e ff2 fs1 fc0 sc0 lsd wsf"> document or the PeerSec Key Generation Utilities </div><div class="t m0 x1 h2 y2f ff2 fs1 fc0 sc0 ls15 ws17">documents included in this package. The key and certificate generation utilities are only </div><div class="t m0 x1 h2 y30 ff2 fs1 fc0 sc0 ls16 ws18">available in specially licensed versions of MatrixSSL. </div><div class="t m0 x1 h2 y31 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h4 y32 ff4 fs3 fc0 sc0 ls17 ws19">Integrating with Applications </div><div class="t m0 x1 h2 y33 ff2 fs1 fc0 sc0 lsd wsf">MatrixSSL is a library that provides a security layer to client and server applications </div><div class="t m0 x1 h2 y34 ff2 fs1 fc0 sc0 ls4 ws5">allowing them to securely communicate with other SSL enabled entities. MatrixSSL is </div><div class="t m0 x1 h2 y35 ff2 fs1 fc0 sc0 ls13 ws15">transport agnostic and can just as easily integrate with an HTTP server as it could with a </div><div class="t m0 x1 h2 y36 ff2 fs1 fc0 sc0 ls18 ws1a">device communicating through a serial port. For simplicity, this developer’s guide will </div><div class="t m0 x1 h2 y37 ff2 fs1 fc0 sc0 ls19 ws1b">assume a socket based implementation for all its examples unless otherwise noted. </div><div class="t m0 x1 h2 y38 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h2 y39 ff2 fs1 fc0 sc0 ls1a ws1c">The term application in this document refers to the client or server application the </div><div class="t m0 x1 h2 y3a ff2 fs1 fc0 sc0 ls1d ws1e">MatrixSSL library is being integrated with. </div><div class="t m0 x1 h2 y3b ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h2 y3c ff2 fs1 fc0 sc0 ls1e ws1f">This document will walk through the specific points in which MatrixSSL should be </div><div class="t m0 x1 h2 y3d ff2 fs1 fc0 sc0 ls19 ws1b">integrated with an application. MatrixSSL APIs should be integrated into the application </div><div class="t m0 x1 h2 y3e ff2 fs1 fc0 sc0 ls1f ws20">during initialization/cleanup, when new secure connections are being setup (handshaking) </div><div class="t m0 x1 h2 y3f ff2 fs1 fc0 sc0 ls1f ws20">and when encrypting/decrypting messages exchanged with peers. </div><div class="t m0 x1 h2 y40 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h2 y41 ff2 fs1 fc0 sc0 ls20 ws21">Refer to the MatrixSSL API document to get familiar with the interface to the library and </div><div class="t m0 x1 h2 y42 ff2 fs1 fc0 sc0 ls1c ws1d">with the example code to see how they are used at implementation. Follow the </div><div class="t m0 x1 h2 y43 ff2 fs1 fc0 sc0 ls19 ws1b">guidelines below when using these APIs to integrate MatrixSSL into an application. </div><div class="t m0 x1 h2 y44 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h6 y45 ff5 fs3 fc0 sc0 ls21 ws22">1. Initialization </div><div class="t m0 x7 h2 y46 ff2 fs1 fc0 sc0 ls22 ws23">MatrixSSL should be initialized as part of the application initialization with a call to </div><div class="t m0 x7 h2 y47 ff6 fs1 fc0 sc0 ls23 ws1">matrixSslOpen. This function takes no parameters and sets up the internal structures </div><div class="t m0 x7 h2 y48 ff2 fs1 fc0 sc0 lsd wsf">needed by the library. </div><div class="t m0 x7 h2 y49 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x7 h2 y4a ff2 fs1 fc0 sc0 lse ws10">In most cases the application will also call matrixSslReadKeys during its initialization. </div><div class="t m0 x7 h2 y4b ff2 fs1 fc0 sc0 ls11 ws26">This function takes the file names of the RSA certificate, private key, and Certificate </div><div class="t m0 x7 h2 y4c ff2 fs1 fc0 sc0 ls9 wsb">Authority files used for authentication and public key encryption. The call extracts the </div><div class="t m0 x7 h2 y4d ff2 fs1 fc0 sc0 ls27 ws27">RSA material and returns an sslKeys_t structure to the application that will be used in </div><div class="t m0 x7 h2 y4e ff2 fs1 fc0 sc0 ls29 ws28">a subsequent call to matrixSslNewSession. matrixSslReadKeys parses through an entire </div></div><div class="pi" data-data='{"ctm":[1.568627,0.000000,0.000000,1.568627,0.000000,0.000000]}'></div></div>

<div id="pf3" class="pf w0 h0" data-page-no="3"><div class="pc pc3 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/622b8aa215da9b288bef99b7/bg3.jpg"><div class="t m0 x1 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">Developer's Guide MatrixSSL 1.8 </div><div class="t m0 x1 h2 y2 ff1 fs0 fc0 sc0 ls2 ws2">Page 3 of 17 Copyright ©2002-2006 PeerSec Networks, Inc. </div><div class="t m0 x7 h2 y4f ff2 fs1 fc0 sc0 ls11 ws26">PEM certificate file so it is a rather CPU intensive task. This needs to be taken into </div><div class="t m0 x7 h2 y50 ff2 fs1 fc0 sc0 lsf ws11">consideration to determine the most logical place for your application to read in its </div><div class="t m0 x7 h2 y51 ff2 fs1 fc0 sc0 ls9 wsb">keys. It can be called a single time at start up to keep the keys in memory for the life of </div><div class="t m0 x7 h2 y52 ff2 fs1 fc0 sc0 ls15 ws17">the application. This is the most common example and should be used in this manner if </div><div class="t m0 x7 h2 y53 ff2 fs1 fc0 sc0 ls11 ws26">the application uses the same certificate file for each connection. Alternatively, it can </div><div class="t m0 x7 h2 y54 ff2 fs1 fc0 sc0 ls11 ws26">be called once for each secure connection and freed immediately after the connection is </div><div class="t m0 x7 h2 y55 ff2 fs1 fc0 sc0 ls2c ws2a">closed. This should be done if the application has multiple certificate files depending </div><div class="t m0 x7 h2 y56 ff2 fs1 fc0 sc0 ls22 ws23">on the identity of the connecting entity or if there is a security concern with keeping the </div><div class="t m0 x7 h2 y57 ff2 fs1 fc0 sc0 ls2d ws2b">RSA keys in memory for extended periods of time. This API can also be used to read a </div><div class="t m0 x7 h2 y58 ff2 fs1 fc0 sc0 ls24 ws24">set of keys for each virtual server, and reused for sessions within that virtual server in </div><div class="t m0 x7 h2 y59 ff2 fs1 fc0 sc0 ls24 ws2c">Apache like environments. </div><div class="t m0 x7 h2 y5a ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x7 h2 y5b ff2 fs1 fc0 sc0 ls20 ws21">Once the application is done with the keys they are freed with a call to </div><div class="t m0 x7 h2 y5c ff6 fs1 fc0 sc0 ls1b ws1">matrixSslFreeKeys. </div><div class="t m0 x7 h2 y5d ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x7 h2 y5e ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h6 y5f ff5 fs3 fc0 sc0 ls2e ws2d">2. Creating a Session </div><div class="t m0 x7 h2 y60 ff2 fs1 fc0 sc0 ls16 ws2e">The next MatrixSSL integration point in the application is to identify when a new </div><div class="t m0 x7 h2 y61 ff2 fs1 fc0 sc0 lse ws10">session is starting. In the case of a client, this is whenever it chooses to begin one since </div><div class="t m0 x7 h2 y62 ff2 fs1 fc0 sc0 ls2f ws2f">only client initiated sessions are supported in MatrixSSL. In the case of a server, a new </div><div class="t m0 x7 h2 y63 ff2 fs1 fc0 sc0 lse ws10">session should be started when the server accepts a connection from a client. In a </div><div class="t m0 x7 h2 y64 ff2 fs1 fc0 sc0 ls15 ws17">socket based application, this would typically happen when the accept socket call </div><div class="t m0 x7 h2 y65 ff2 fs1 fc0 sc0 ls13 ws15">returns. The application sets up a new session with the API matrixSslNewSession. The </div><div class="t m0 x7 h2 y66 ff2 fs1 fc0 sc0 ls33 ws1">returned ssl_t value will become the input parameter for most of the remaining APIs </div><div class="t m0 x7 h2 y67 ff2 fs1 fc0 sc0 ls13 ws15">that act at a session level. </div><div class="t m0 x7 h2 y68 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x7 h2 y69 ff2 fs1 fc0 sc0 ls36 ws32">The required input parameters to matrixSslNewSession are the key structure from the </div><div class="t m0 x7 h2 y6a ff2 fs1 fc0 sc0 ls37 ws33">previous call to matrixSslReadKeys and the flag SSL_FLAGS_SERVER or 0 (for a </div><div class="t m0 x7 h2 y6b ff2 fs1 fc0 sc0 ls12 ws35">client session). In the commercial version of MatrixSSL the server may also choose to </div><div class="t m0 x7 h2 y6c ff2 fs1 fc0 sc0 ls19 ws1b">include the flag SSL_FLAGS_CLIENT_AUTH if client authentication is required. The </div><div class="t m0 x7 h2 y6d ff2 fs1 fc0 sc0 ls3a ws36">MatrixSSL library must have be compiled with USE_CLIENT_AUTH defined in order </div><div class="t m0 x7 h2 y6e ff2 fs1 fc0 sc0 ls4 ws5">to use this flag. </div><div class="t m0 x7 h2 y6f ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x7 h2 y70 ff2 fs1 fc0 sc0 ls12 ws35">For client cases, there is an optional sessonId parameter that identifies a previously </div><div class="t m0 x7 h2 y71 ff2 fs1 fc0 sc0 ls34 ws38">open session to resume a session. A session id can be retrieved from a call to </div><div class="t m0 x7 h2 y72 ff6 fs1 fc0 sc0 ls3d ws1">matrixSslGetSessionId once a session has been negotiated and before it is deleted. The </div><div class="t m0 x7 h2 y73 ff2 fs1 fc0 sc0 ls3e ws39">session id parameter must always be NULL for server implementations. </div><div class="t m0 x7 h2 y74 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x7 h2 y75 ff2 fs1 fc0 sc0 lsd wsf">A final consideration at this point of integration is whether or not to register a </div><div class="t m0 x7 h2 y76 ff2 fs1 fc0 sc0 ls22 ws23">certificate validation callback function with the matrixSslSetCertValidator API. This </div><div class="t m0 x7 h2 y77 ff2 fs1 fc0 sc0 ls40 ws3b">routine takes the SSL session and a function pointer as arguments. The registered </div><div class="t m0 x7 h2 y78 ff2 fs1 fc0 sc0 ls1f ws20">function will be invoked during the portion of the handshake process in which the </div><div class="t m0 x7 h2 y79 ff2 fs1 fc0 sc0 ls41 ws3c">certificate is being verified. This API should be used when the MatrixSSL default </div><div class="t m0 x7 h2 y7a ff2 fs1 fc0 sc0 lsa wsc">certificate validation is not deemed sufficient or if the application would like to expose </div><div class="t m0 x7 h2 y7b ff2 fs1 fc0 sc0 ls42 ws3d">the certificate information to the user for any reason. In the commercial version this </div><div class="t m0 x7 h2 y7c ff2 fs1 fc0 sc0 lsa wsc">callback registration only makes sense on the server side if client authentication is </div></div><div class="pi" data-data='{"ctm":[1.568627,0.000000,0.000000,1.568627,0.000000,0.000000]}'></div></div>

<div id="pf4" class="pf w0 h0" data-page-no="4"><div class="pc pc4 w0 h0"><img class="bi x0 y0 w1 h1" alt="" src="https://static.pudn.com/prod/directory_preview_static/622b8aa215da9b288bef99b7/bg4.jpg"><div class="t m0 x1 h2 y1 ff1 fs0 fc0 sc0 ls0 ws0">Developer's Guide MatrixSSL 1.8 </div><div class="t m0 x1 h2 y2 ff1 fs0 fc0 sc0 ls2 ws2">Page 4 of 17 Copyright ©2002-2006 PeerSec Networks, Inc. </div><div class="t m0 x7 h2 y4f ff2 fs1 fc0 sc0 lsa wsc">being used as the application will be receiving the client certificate as part of the </div><div class="t m0 x7 h2 y50 ff2 fs1 fc0 sc0 ls3f ws1">handshake. </div><div class="t m0 x7 h2 y51 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x7 h2 y52 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x1 h6 y7d ff5 fs3 fc0 sc0 ls43 ws3e">3. Handshaking </div><div class="t m0 x7 h2 y7e ff2 fs1 fc0 sc0 lsa wsc">With the session now established, a client initiates a handshake by first constructing the </div><div class="t m0 x7 h2 y7f ff2 fs1 fc0 sc0 ls24 ws24">CLIENT_HELLO message with a call to matrixSslEncodeClientHello. The client </div><div class="t m0 x7 h2 y80 ff2 fs1 fc0 sc0 ls22 ws23">sends the constructed data to the server. When the server receives notice that a client is </div><div class="t m0 x7 h2 y81 ff2 fs1 fc0 sc0 ls19 ws1b">requesting a secure communication session and the function matrixSslNewSession has </div><div class="t m0 x7 h2 y82 ff2 fs1 fc0 sc0 ls11 ws26">been called to create a new session structure the application can then read in the client </div><div class="t m0 x7 h2 y83 ff2 fs1 fc0 sc0 ls29 ws28">message data. All incoming messages should be passed to matrixSslDecode which then </div><div class="t m0 x7 h2 y84 ff2 fs1 fc0 sc0 ls15 ws17">processes the message and drives the handshake through the built-in SSLv3 state </div><div class="t m0 x7 h2 y85 ff2 fs1 fc0 sc0 ls45 ws41">machine. The parameters to matrixSslDecode include the SSL structure returned from </div><div class="t m0 x7 h2 y86 ff2 fs1 fc0 sc0 ls12 ws35">the call to matrixSslNewSession, input and output buffers, and alert and error output </div><div class="t m0 x7 h2 y87 ff2 fs1 fc0 sc0 ls27 ws27">parameters. Refer to the API documentation for more details. </div><div class="t m0 x7 h2 y88 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x7 h2 y89 ff2 fs1 fc0 sc0 ls46 ws1">The matrixSslDecode API is a powerful function that processes handshake messages </div><div class="t m0 x7 h2 y60 ff2 fs1 fc0 sc0 lsa ws15">for clients and servers as well as decoding application data. Its return code tells the </div><div class="t m0 x7 h2 y61 ff2 fs1 fc0 sc0 lsd wsf">application what the message was and how it is to be handled. </div><div class="t m0 x7 h2 y62 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x7 h2 y63 ff2 fs1 fc0 sc0 lsd wsf">The steps below outline the proper usage of matrixSslDecode on the server side when </div><div class="t m0 x7 h2 y64 ff2 fs1 fc0 sc0 ls2f ws2f">handshaking. A sockets based implementation is assumed in these steps. </div><div class="t m0 x7 h2 y65 ff2 fs1 fc0 sc0 ls1 ws1"> </div><div class="t m0 x8 h2 y66 ff2 fs1 fc0 sc0 ls30 ws43">1. The applications reads the client data off the socket with recv </div><div class="t m0 x8 h2 y67 ff2 fs1 fc0 sc0 ls1 ws1">2. matrixSslDecode is called with the client data </div><div class="t m0 x8 h2 y68 ff2 fs1 fc0 sc0 ls1a ws1c">3. The return value from matrixSslDecode is tested to see what action the </div><div class="t m0 x9 h2 y69 ff2 fs1 fc0 sc0 ls30 ws43">application is required to do with the output buffer. The list of possible return </div><div class="t m0 x9 h2 y6a ff2 fs1 fc0 sc0 ls30 ws43">values and appropriate action include: </div><div class="t m0 xa h2 y6b ff2 fs1 fc0 sc0 ls20 ws21">a. SSL_SEND_RESPONSE - This value indicates the message was part </div><div class="t m0 xb h2 y6c ff2 fs1 fc0 sc0 ls13 ws15">of the SSLv3 standard and a reply is expected. The application should </div><div class="t m0 xb h2 y6d ff2 fs1 fc0 sc0 ls49 ws45">send the output buffer to the client with send and then call </div><div class="t m0 xb h2 y6e ff6 fs1 fc0 sc0 ls47 ws1">matrixSslDecode again to see if any more message data needs to be </div><div class="t m0 xb h2 y6f ff2 fs1 fc0 sc0 ls4 ws1">decoded. </div><div class="t m0 xa h2 y70 ff2 fs1 fc0 sc0 ls42 ws3d">b. SSL_ERROR – This value indicates there has been an error while </div><div class="t m0 xb h2 y71 ff2 fs1 fc0 sc0 ls4b ws47">attempting to decode the data or that a bad message was sent. The </div><div class="t m0 xb h2 y72 ff2 fs1 fc0 sc0 lsf ws11">application should attempt to send the out buffer to the client as a reply </div><div class="t m0 xb h2 y73 ff2 fs1 fc0 sc0 ls20 ws21">and then close the socket. </div><div class="t m0 xa h2 y74 ff2 fs1 fc0 sc0 lse ws10">c. SSL_ALERT – This value indicates the message was an alert sent </div><div class="t m0 xb h2 y75 ff2 fs1 fc0 sc0 lsa wsc">from the client and the application should close the socket. </div><div class="t m0 xa h2 y76 ff2 fs1 fc0 sc0 lsa wsc">d. SSL_PARTIAL – This value indicates that the input buffer was an </div><div class="t m0 xb h2 y77 ff2 fs1 fc0 sc0 lsf ws11">incomplete message or record (or no data at all to parse). If the </div><div class="t m0 xb h2 y78 ff2 fs1 fc0 sc0 ls11 ws48">handshake is incomplete (!matrixSslHandshakeIsComplete()), the </div><div class="t m0 xb h2 y79 ff2 fs1 fc0 sc0 lsf ws11">application must retrieve more data from the socket with recv and call </div><div class="t m0 xb h2 y7a ff6 fs1 fc0 sc0 ls47 ws1">matrixSslDecode with then entire record. If the handshake is </div><div class="t m0 xb h2 y7b ff2 fs1 fc0 sc0 ls22 ws23">complete, the caller can decide whether more data is expected at this </div><div class="t m0 xb h2 y7c ff2 fs1 fc0 sc0 ls4b ws4b">point or not. </div></div><div class="pi" data-data='{"ctm":[1.568627,0.000000,0.000000,1.568627,0.000000,0.000000]}'></div></div>