CLI usage

The CLI is the non-interactive interface for senders, test scripts, and agents.

Install

curl -fsSLO https://stashvlt.astm.co.za/download/stashvlt-cli-linux-x64.tar.gz
mkdir -p ~/.local/bin/stashvlt
 tar -xzf stashvlt-cli-linux-x64.tar.gz -C ~/.local/bin/stashvlt
~/.local/bin/stashvlt/StashVlt.Cli help

Create a recipient identity

StashVlt.Cli identity --store ~/.stashvlt --json > recipient.json

Configure the online relay

StashVlt.Cli configure --store ~/.stashvlt \
  --relay https://stashvlt.astm.co.za \
  --inbox blind-demo-inbox --json

Create a sender signing key

StashVlt.Cli sender-key --store ~/.stashvlt-sender --key-id clinic-demo --json > sender-public.json

For the current test CLI, push expects PEM key files. Keep private key files outside shared folders and logs.

List and decrypt

StashVlt.Cli list --store ~/.stashvlt --json
StashVlt.Cli decrypt --store ~/.stashvlt --relay https://stashvlt.astm.co.za --id pkg_... --json

Command reference

identity --store DIR [--json]
configure --store DIR --relay URL --inbox BLIND_ID [--allow-insecure-http] [--json]
settings --store DIR [--json]
sender-key --store DIR --key-id ID [--json]
trust-sender --store DIR --key-id ID --name NAME --public-key-file PATH [--json]
trusted-senders --store DIR [--json]
push --relay URL --inbox BLIND_ID --recipient-key-id ID --recipient-public-key-file PATH --sender-key-id ID --sender-private-key-file PATH (--text TEXT|--file PATH) [--tag k=v] [--json]
list (--store DIR|--relay URL --inbox BLIND_ID) [--json]
get --relay URL --id PACKAGE_ID [--json]
decrypt --store DIR --relay URL --id PACKAGE_ID [--json]