jordan 34f349e510 Used codespell and fixed obvious typos. | 1 éve | |
---|---|---|
.. | ||
README.md | 1 éve | |
async_client.c | 1 éve | |
async_server.c | 1 éve | |
async_tls.c | 1 éve | |
async_tls.h | 1 éve | |
include.am | 1 éve |
Supported with:
--enable-cryptocb
)--enable-pkcallbacks
)Requires files from https://github.com/wolfSSL/wolfAsyncCrypt
See async-check.sh
for how to setup.
Tested with:
./configure --enable-asynccrypt --enable-rsa --disable-ecc
./configure --enable-asynccrypt --disable-rsa --enable-ecc
./configure --enable-asynccrypt --enable-cryptocb --enable-rsa --disable-ecc
./configure --enable-asynccrypt --enable-cryptocb --disable-rsa --enable-ecc
./configure --enable-asynccrypt --enable-pkcallbacks --enable-rsa --disable-ecc
./configure --enable-asynccrypt --enable-pkcallbacks --disable-rsa --enable-ecc
make
./examples/async/async_server
./examples/async/async_client 127.0.0.1
When a cryptogaphic call is handed off to hardware it return WC_PENDING_E
up to caller. Then it can keep calling until the operation completes. For some platforms it is required to call wolfSSL_AsyncPoll
. At the TLS layer a "devId" (Device ID) must be set using wolfSSL_CTX_SetDevId
to indicate desire to offload cryptography.
For further design details please see: https://github.com/wolfSSL/wolfAsyncCrypt#design
For questions please email support@wolfssl.com