EngineStates

States for SSL engines.

version(WITH_HUNT_SECURITY)

final

class EngineStates {

enum int STATE_NEW;

enum int STATE_MODE_SET;

enum int STATE_HANDSHAKE_STARTED;

enum int STATE_HANDSHAKE_COMPLETED;

enum int STATE_READY_HANDSHAKE_CUT_THROUGH;

enum int STATE_READY;

enum int STATE_CLOSED_INBOUND;

enum int STATE_CLOSED_OUTBOUND;

enum int STATE_CLOSED;

}

Members

Variables

STATE_CLOSED enum int STATE_CLOSED;: The engine has been closed.
STATE_CLOSED_INBOUND enum int STATE_CLOSED_INBOUND;: The inbound direction of the engine has been closed.
STATE_CLOSED_OUTBOUND enum int STATE_CLOSED_OUTBOUND;: The outbound direction of the engine has been closed.
STATE_HANDSHAKE_COMPLETED enum int STATE_HANDSHAKE_COMPLETED;: Listeners of the handshake have been notified of completion but the handshake call hasn't returned.
STATE_HANDSHAKE_STARTED enum int STATE_HANDSHAKE_STARTED;: The handshake has been started
STATE_MODE_SET enum int STATE_MODE_SET;: The client/server mode of the engine has been set.
STATE_NEW enum int STATE_NEW;: The engine is constructed, but the initial handshake hasn't been started
STATE_READY enum int STATE_READY;: The handshake call has returned and the listeners have been notified. Ready to begin writing data.
STATE_READY_HANDSHAKE_CUT_THROUGH enum int STATE_READY_HANDSHAKE_CUT_THROUGH;: The handshake call returned but the listeners have not yet been notified. This is expected behaviour in cut-through mode, where SSL_do_handshake returns before the handshake is complete. We can now start writing data to the socket.

Meta

Source

See Implementation

hunt net secure conscrypt SSLUtils classes