Skip to main content

Module client_auth

Module client_auth 

Source
Expand description

The client listener’s verdict on a challenge response.

The kernel TCP and DPDK transports each run the handshake over their own sockets, but decide it here, so the two cannot disagree about which keys may connect as a client. The DPDK path cannot be exercised without the hardware; this is how its decision is tested all the same.

Public for a listener of the application’s own that admits the node’s client keys, an event publisher’s subscribers say: calling verify_client applies the client listener’s rule exactly, rather than a copy of it that has to be kept in step by hand.

Enums§

ClientAuthError
Why the client listener refused a challenge response.

Functions§

verify_client
Decide a client’s challenge response: the key must be listed, under a role that may connect as a client, and must have signed nonce. Returns the connection’s role, as the runtime carries it: the operator, or an application role as its index in the role table.