Configure sandbox SSH key
Adds an OpenSSH public key to the running sandbox so the caller can SSH as user user. The response carries machineIp, which is the host to connect to on port 22.
This is also how you reach your own machine from inside a sandbox without the CLI: authorize the key, then open a reverse tunnel with stock OpenSSH, and a port on your machine answers at 127.0.0.1:<port> inside the sandbox for as long as the ssh process runs.
boat forward <id> --reverse --local 7777 is the same tunnel with the key handling and redial done for you.
Authorizations
Boat bearer token in the form boat_.... Service API keys authenticate sandbox operations.
Path Parameters
Public Sandbox id returned by create/list/get sandbox calls.
^bx_[23456789abcdefghjkmnpqrstuvwxyz]{8}$Body
Public SSH key in OpenSSH format. Private keys are rejected.
"ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAA... user@host"
Response
SSH key setup result.
true
Stable success envelope discriminator added by v1.
"user"
Public IPv4 host:port that forwards to the sandbox SSH server, set only when the machine has no public IPv4 of its own. Connect with ssh -p <port> user@<host>.
"203.0.113.10:22001"
The sandbox SSH server's public host key. Pin it in known_hosts.
"ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAA..."