History

Sean Parkinson 8e9810e87e ssl.c: Move functions out to separate files

Moved E[CD][25519||448] APIs to pk.c
Move public key PEM APIs to pk.c.
Move wolfSSL loading and using of private keys and certificates to
ssl_load.c
Move PKCS#7 and PKCS#12 APIs to ssl_p7p12.c.
Move session and session cache APIs to ssl_sess.c.
Other minor fixes.

2024-04-16 10:30:59 +10:00

client

…

server

…

shared

…

wolfssl_new_azsphere

ssl.c: Move functions out to separate files

2024-04-16 10:30:59 +10:00

include.am

…

README.md

…

user_settings.h

…

README.md

wolfSSL for Microsoft Azure Sphere Devices in MSVS 2019

Description

This directory contains the Visual Studio CMake Project that is targeted for the visual studio 2019 Azure Sphere plugin.

Limitations

The example includes a client and server executable but the main.c app only runs the server by default. main.c can be manually modified to run the client instead if desired.

By default the main.c app include the hardware definitions for MT3620-mini. It can be manually modified to include hardware definitions for MT3620, or avnet MT3620 instead.

The app relies on a wolfSSL static library project, app and library are built by the CMakeLists.txt located in IDE/MSVS-2019-AZSPHERE/wolfssl_new_azsphere/CMakeLists.txt. The library and app use user_settings.h to enable and disable features.

Set Up Steps

Setup your Azure Sphere device. Install Azure Sphere Set up an account Claim your device Configure networking
Open the local folder IDE/MSVS-2019-AZSPHERE/wolfssl_new_azsphere in MSVS 2019
From the file menu select "Build" dropdown
- Click: Rebuild All option
Connect your Azure Sphere MT3620-mini Development Board using USB.
Test the server.
- Run server(Azure Sphere) using: Debug->'Start new instance'
- Run the following wolfSSL example client command inside wolfssl directory.

./examples/client/client -h "Server IP Address" -p 11111 -A ./certs/ca-cert.pem

For other information please refer to the README in IDE/VS-AZURE-SPHERE