dspk clients
Who may connect to serve: enroll, revoke, list clients (certificates from the server’s own authority)
dspk clients [OPTIONS] <COMMAND>Options
--auth-dir <AUTH_DIR>: envDSPK_SERVE_AUTH_DIR
The server’s authority folder (default: <data dir>/serve, e.g. ~/.local/share/dspk/serve)
dspk clients enroll
Section titled “dspk clients enroll”Issue a client its certificate (read only unless –control) and write it to a file to give to that client (dspk receive --identity <file>)
dspk clients enroll [OPTIONS] <NAME>Arguments
<NAME>
Who the client is: a person or a machine (letters, digits, ‘.’, ‘_’, ‘-’)
Options
--auth-dir <AUTH_DIR>: envDSPK_SERVE_AUTH_DIR
The server’s authority folder (default: <data dir>/serve, e.g. ~/.local/share/dspk/serve)--control
Also configure, start and stop jobs, and write (not only read recordings)--out <OUT>
Where to write the client’s file (default: <name>.dspk-identity.pem here;-: to standard output, e.g. throughpodman exec … > file, so no copy stays on the server); never overwritten. Never put it under the server’s data root
dspk clients revoke
Section titled “dspk clients revoke”Refuse a client from its next connection on
dspk clients revoke [OPTIONS] <NAME>Arguments
<NAME>
Options
--auth-dir <AUTH_DIR>: envDSPK_SERVE_AUTH_DIR
The server’s authority folder (default: <data dir>/serve, e.g. ~/.local/share/dspk/serve)
dspk clients list
Section titled “dspk clients list”The clients enrolled, active and revoked
dspk clients list [OPTIONS]Options
--auth-dir <AUTH_DIR>: envDSPK_SERVE_AUTH_DIR
The server’s authority folder (default: <data dir>/serve, e.g. ~/.local/share/dspk/serve)