You are not logged in. Please login or register.
Active topics Unanswered topics
Welcome to the wolfSSL Forums!
Please post questions or comments you have about wolfSSL products here. It is helpful to be as descriptive as possible when asking your questions.
References
Stable Releases - download stable product releases.
Development Branch - latest development branch on GitHub.
wolfSSL Manual - wolfSSL (formerly CyaSSL) product manual and API reference.
Search options
Thank you so much for the information, has been of great value.
Really? amazing! . And tell me, is it the same with wolf_write and wolf_read?
Hi again!
I've been cheking the function:
int wolfSSL_accept(WOLFSSL* ssl)
Seems like I have to 'unroll' whe 'while' statemtns in the final switch:
switch (ssl->options.acceptState)
Any other built in alternative?
Hello !
I'm trying to make wolfSSL embedded ssl work in an OS-less, non blocking I/o environment. Is a "superloop" app. Is the synchronization of many state machines, one of them read queued buffers to transmit, and transmit them. The server state machine has to post data, leave the control of the state machine and then is state will be evaluated when the data is transmitted again.
My worried is about the handshaking. Since basically all it's done inside "makeHandshake()" in some moment it will block. Is there a build in option to avoid this behavior and make it work with this constraints.
Thank you in advance!
Posts found: 4
Generated in 0.015 seconds (95% PHP - 5% DB) with 5 queries