Skip to main content

Vault Encryption and Device Access

Understand ShellMate Vault credentials, recovery material, device authorization and the limits of application controls across SSH and AWS connection workflows.

Vault credentials and integration tokens

Saved Vault secrets are encrypted on the client and decrypted locally for authorized desktop use. Shared cloud integration tokens are encrypted server-side for provider reads and are not zero-knowledge Vault items. Host labels and observed system details are ordinary metadata.

Recovery and local key material

Follow the current desktop setup and recovery instructions for your ShellMate Key (.smk). Account password resets restore sign-in, not lost Vault keys. Keep recovery material separate from your device and validate recovery before relying on it.

This guide does not promise BIP-39 compatibility, X25519 key exchange or hardware-backed attestation across every version. Consult the protocol and release documentation for the version you deploy.

Connection modes and revocation

SSH authentication depends on the configured host and credential method. Certificate-based access requires its own setup; not every connection creates an SSH certificate. AWS SSM is a separate workflow with AWS prerequisites.

Revoking application access does not erase credentials already copied or prove that an established remote session has ended. Check remote accounts, active sessions and host logs during offboarding.

Operational limits

Protect endpoints and local key material. This page does not guarantee complete memory erasure, universal credential expiry, uninterrupted service or any particular production redundancy configuration.