Supplied buffer is consumed to produce bytes.
Supplied buffer is consumed to produce bytes.
It is expected that buffer is in write-ready state.
Buffer is cleared to be fresh to receive new output data
With supplied bytes fill the supplied buffer.
With supplied bytes fill the supplied buffer. Note that this may create new buffer, if supplied buffer is not able to hold bytes supplied.
This expected supplied buffer to be in write-ready state, while resulting buffer is in read-ready state
Creates new buffer of desired
size.
Creates new buffer of desired
size. Resulting buffer is ready to be written at full capacity.
All data in buffer are lost
Buffer to resize, potentially with some data
Desired size of new buffer
runs all available tasks , retruning when tasks has been finished *
Perform un-wrap
operation on engine.
Perform un-wrap
operation on engine.
Note that apart of performing the un-wrap, this handles following:
- acquires un-wrap lock
- if the un-wrap resulted in NEED_TASK, then tha task i executed with supplied S
strategy
- If the buffer UNDERFLOW is returned then we memoize the bytes with signal received and request for more bytes to input
- If the buffer OVERFLOW
As the last operation this releases the acquired lock to prevent concurrent unwraps to be executed simultaneously.
SSL Engine this operates on
Bytes to wrap
Contains reference to active buffers used to perform I/O. The first buffer is buffer with encrypted data. Second buffer is buffer with decrypted data. Second buffer is always empty, when this finishes, while first buffer may contain data to be used at next invocation of unwrap.
Perform wrap
operation on engine.
Perform wrap
operation on engine.
Note that apart of performing the wrap, this handles following:
- acquires wrap lock
- if the wrap resulted in NEED_TASK, then tha task i executed with supplied S
strategy
- If the buffer UNDER/OVERFLOW is signalled new destination buffer is allocated and returned
As the last operation this releases the acquired wrap lock, to prevent two concurrent wraps to be executed.
SSL Engine this operates on
Bytes to wrap
Contains reference to active buffers used to perform I/O. The first buffer is buffer with application data. Second buffer is buffer with encrypted data. Second buffer is always empty, when this finishes, while first buffer may contain data to be used at next invocation of wrap.
helper to perform wrap/unwrap *