C->S, client wants to check if the server is active.

S->C, server responds to the client that it is active.

C->C, S->S, used to test that Redis is delivering messages.

C->S, client wants to establish an encrypted session with the server.

S->C, server responds if it is able to set up a session.

C->S, client starts by requesting that the session follow some parameters.

S->C, server acknowledges that it will respect the client's wishes.

C->S, S->C, sent by either party to indicate session is closed.

S->C, C->S, the party sending a file uses this message to transfer data.

S->C, C->S, the party sending a file indicates that they are done.

C->S, empty message to signal that client is still active.

S->C, empty message to signal that server is still active.

C->S, client is sending commands to the server's PTY.

S->C, server is sending output from its PTY.

C->S, client wants to adjust the size of the server's PTY.

Enum value maps for PublicMessage_MessageType.

Enum value maps for PublicMessage_MessageType.

Enum value maps for SessionMessage_MessageType.

Enum value maps for SessionMessage_MessageType.

Enum value maps for SessionMode.

Enum value maps for SessionMode.

An encrypted session message contains a session message in ciphertext format.

Any message in transit must be in one of the following formats.

Public messages are sent without encryption between any server and client.

Session messages are sent with encryption guarantees between a server and client.