Skip to content
ZyncDocsGitHub Download Zync

Vault

Keep shared SSH and VNC passwords, private keys and matching user certificates encrypted in an optional on-device vault.

The Local Vault is an optional encrypted store for credentials that Zync uses on this device. You choose the passphrase and keep the recovery key. Zync does not host your vault or your credentials.

The Vault encrypts stored passwords, private keys, optional matching SSH user certificates, and supported provider credentials at rest. It uses Argon2id key derivation and authenticated encryption (AEAD). SSH hosts and saved VNC profiles refer to credentials by a stable identity, so changing or restoring a credential does not require recreating each linked connection.

The Vault also supports:

  • A recovery key for regaining access if you forget the vault passphrase.
  • Optional Remember on this device, which stores unlock material in the operating system credential store.
  • Credential revisions, so you can review and restore an earlier encrypted revision.
  • Migration of supported credentials from older local connection records into the Vault.

Open Vaults in the Zync sidebar. On first use:

  1. Create a strong vault passphrase.
  2. Save the recovery key somewhere offline and safe.
  3. Decide whether to enable Remember on this device.

When you add or edit an SSH host, choose Vault storage for a password or private key. The host record keeps a reference to the credential instead of embedding the raw secret.

Password entries can be used by SSH hosts and saved VNC profiles. Each connection explicitly selects its credential; saving a password for one connection does not assign it to others. Existing saved passwords and their revision history remain usable.

In a VNC profile, choose Saved Vault credential to select a Password entry, or Save password to Vault to create one while saving the profile. The profile stores only the credential reference. See VNC passwords.

Key files are still a first-class option. A key can remain at its existing path and be used by SSH without being copied into the Vault. If you later import a key into the Vault, the original file is not needed for the vault-backed connection.

AI provider API keys follow a stricter policy: they are encrypted in the Local Vault, remain on this device, and are excluded from credential sync and full vault backup exports.

You can also add a password or private key directly from the Vault credential list before assigning it to a connection.

  • Assign lets you manage which saved SSH hosts use a credential. Review the selected hosts before saving. Link VNC profiles from their own authentication controls.
  • Rotate replaces a credential’s secret while keeping its identity. Linked connections use the updated secret on their next authentication. Update the matching password or authorized key on the remote system as needed; changing Vault does not change the server.
  • History lists earlier encrypted revisions. Choose Restore beside a revision and confirm to make it current. The current secret is saved to history first, and the credential keeps its identity.

Updating a credential does not reauthenticate an already connected SSH session. Zync can offer to disconnect affected SSH hosts after assignment, rotation or revision restore. Reconnect when you want to authenticate with the updated credential.

In Zync 2.37.0 and later, an SSH private-key credential can include an optional matching OpenSSH user certificate. Paste its contents or use Import file when creating or rotating the key. Import fills the draft; it does not retain a dependency on the original file after saving.

Credential details let you attach, replace or remove only the certificate without re-entering the stored private key or passphrase. Zync checks the certificate’s key pairing and signature. An expired or not-yet-valid certificate can remain in saved history, but connecting enforces its validity period and the server’s authorization policy.

The attachment is encrypted with the key and follows its existing credential revision history and any explicit encrypted credential sync or backup. Renewed files are not reread automatically: replace the Vault attachment and reconnect. When rotating the whole key, leaving its certificate blank removes the previous attachment.

A host’s selected certificate file overrides its Vault attachment. Attach an OpenSSH user certificate to an SSH private key, not a password or TLS certificate credential. See connection certificates for file-based renewal and authentication behavior.

Vault-backed connections ask you to unlock before connecting or testing. If you started an explicit Connect, Test connection, or Open VNC action, completing unlock lets that action continue. Cancelling unlock stops that attempt.

Merely opening or restoring a tab does not silently connect a vault-backed SSH host or saved VNC profile. Use its connection action when ready. Unlocking Vault from the Vault page alone does not start those connections.

Remember-on-device is convenient on a personal computer, but anyone who can use your unlocked operating-system session may be able to use vault-backed connections until the cache expires or you choose Forget device.

Only one Zync process can open a local vault at a time. If another window reports Vault In Use, switch to the existing Zync instance instead of creating another vault.

These are related but separate features:

Feature Purpose
Local Vault Optional, on-device encrypted credential storage.
Sync & Backup Optional encrypted upload and restore using your Google Drive.
Public URLs Separate beta sharing service for selected localhost ports.

Drive sync is not required to use the Local Vault. If you enable it, read Sync & Backup before uploading credentials or other workspace data.

If you know the current passphrase, use the Vault security controls to change it. If you forgot it but kept the recovery key, use the recovery flow to regain access and set a new passphrase.

If both unlock methods are lost, reset the local vault on this device and create a new one. Resetting removes the local encrypted vault and clears local host references to its credentials. It does not delete encrypted records stored in your Google Drive, but those records still require their sync passphrase and a working local vault to use.

Open the host’s authentication settings and review its linked Vault credential. Zync can repair stale stored record locations when the stable credential identity still exists. If the credential was deleted, choose another credential or create a replacement rather than recreating the entire host.

  • Sync & Backup for optional Google Drive storage and restore behavior.
  • Security for data boundaries, recovery guidance, and Public URLs exposure.