MatrixSSL Getting Started Guide
MatrixSSL 3.1.2
Overview 1 Who Is This Document For? 1 Documentation Style Conventions 1 Compiling and Testing MatrixSSL 2 POSIX Platforms with Makefiles 2 Preparation 2 Building the source 2 Self-Test Application 3 Sockets-Bad Client and Server Applications 4 Debug Builds vs. Relea Builds 6 WIN32 Platforms using Visual Studio Projects 7 Preparation 7 Building the source 7 Self-Test Application 8 Sockets-Bad Client and Server Applications 10 Debug Builds vs. Relea Builds 14 Mac OS X Platforms using Xcode Projects 15
PeerSec Networks, Inc. 410 Broadway Ave E. #205 Seattle, WA 98102 T 425.646.7850 F 206.501.4366
Overview
This Getting Started Guide explains how to quickly compile and test the MatrixSSL package on supported reference platforms. This guide also contains instructions on building and running the client and rver applications provided in the package.
Who Is This Document For?
•Software developers working on a supported platform that want to create a development environment for integrating MatrixSSL curity into a custom application
•Software developers who want to port MatrixSSL to a new platform
•Anyone wanting to learn more about MatrixSSL
Documentation Style Conventions
•File names and directory paths are italicized.
•C code literals are distinguished with the Monaco font.
Compiling and Testing MatrixSSL
POSIX Platforms with Makefiles
The POSIX classification in MatrixSSL encompass support for veral operating system platforms including Mac OSX 10.5 and most UNIX/LINUX varieties. This is the default platform for the Makefile system that is provided in the package and should be the first build option if you are unsure of your platform configuration.
Preparation
The development platform must have the following tools installed:
•The tar archiver for unzipping the package (or other decompression utility
supporting .TGZ files)
•A C source code compiler and linker (GCC is the default in the provided Makefile system)
•The make tool
Building the source
1.From the command prompt, unpack the zipped tar image.
$ tar -
2.Change directory to the root of the package and build the MatrixSSL library .带王字大全
$ cd matrixssl-3-1-2-open
$ make
3.Confirm there were no compile errors and that the MatrixSSL libraries have been
built. A successful build will result in a libmatrixssl shared and static library.
Applications interface with this library through the MatrixSSL public API t which is documented in the MatrixSSL_API PDF file included in the distribution.
Self-Test Application
Source code for a lf-test application to exerci the SSL handshake and data exchange functionality of the MatrixSSL library is provided with the package. The following optional steps will enable the developer to build and run the test application to confirm the SSL protocol is fully functional.
1.Having successfully built the static library from the Building the source steps above,
change directories to the test folder where the sslTest.c source is located and compile the application.
$ cd matrixssl/test
$ make
2.Run the sslTest application from the command line. This sample output shows a
successful run of the test using the default configuration of the open source package.
$ ./sslTest
Testing TLS_RSA_WITH_AES_128_CBC_SHA suite
Standard handshake test
PASSED: Standard handshake
Re-handshake test (client-initiated)飞蚊症是什么症状
PASSED: Re-handshake
Resumed handshake test (new connection)
PASSED: Resumed handshake
自动洗衣机怎么用
Re-handshake test (rver initiated)
PASSED: Re-handshake
Resumed Re-handshake test (client initiated)
长妈妈与山海经
PASSED: Resumed Re-handshake
Resumed Re-handshake test (rver initiated)
PASSED: Resumed Re-handshake
Change cert callback Re-handshake test
PASSED: Upgrade cert callback Re-handshake
Change keys Re-handshake test
PASSED: Upgrade keys Re-handshake
Change cipher suite Re-handshake test
PASSED: Change cipher suite Re-handshake
晏的读音
Testing SSL_RSA_WITH_3DES_EDE_CBC_SHA suite
Standard handshake test
PASSED: Standard handshake
Re-handshake test (client-initiated)
PASSED: Re-handshake
Resumed handshake test (new connection)
PASSED: Resumed handshake
Re-handshake test (rver initiated)
PASSED: Re-handshake
Resumed Re-handshake test (client initiated)
PASSED: Resumed Re-handshake
Resumed Re-handshake test (rver initiated)
PASSED: Resumed Re-handshake
Change cert callback Re-handshake test
PASSED: Upgrade cert callback Re-handshake
Change keys Re-handshake test
PASSED: Upgrade keys Re-handshake
我的好朋友作文600字Change cipher suite Re-handshake test
PASSED: Change cipher suite Re-handshake
Sockets-Bad Client and Server Applications
Source code for TCP/IP sockets-bad client and rver applications are provided with the MatrixSSL package. The following optional steps will enable the developer to build and run the applications to confirm the development platform is configured for MatrixSSL integration.
1.Having successfully built the static library from the Building the source steps above,教师法
change directories to the apps folder where the client.c and rver.c source is located and compile the applications.
$ cd apps
$ make一间小屋
2.Run the rver application from the command line.
$ ./rver
