mShell mShelldocs
← 返回首页← Home

安全 · 同步Security & Sync

凭证的归宿,是硬件级保险箱。

安全模型

  • 私钥优先存入 Secure Enclave,受硬件绑定、永不离开设备。
  • 密码与可同步密钥经 iCloud 钥匙串端到端加密,连 Apple 也读不到。
  • 主机指纹 TOFU 校验——首次信任、之后变更即拦截(防中间人)。
  • 启动生物识别解锁;复制后自动清空剪贴板
  • 所有配置本地存储,离线可用、无需账号。

iCloud 同步

在「设置」开启「iCloud 同步」:主机与分组经 CloudKit 私有库同步,密码与私钥经 iCloud 钥匙串端到端加密同步到登录同一账号的设备。

同步开关切换后需重启 App 生效(容器在启动时绑定)。Secure Enclave 密钥受硬件绑定,不参与同步。

Credentials belong in a hardware vault.

Security model

  • Private keys go to the Secure Enclave first — hardware-bound, never leaving the device.
  • Passwords and syncable keys are end-to-end encrypted in the iCloud Keychain, unreadable even to Apple.
  • TOFU host-fingerprint checks — trust on first use, block on change (anti-MITM).
  • Biometric unlock on launch; clipboard auto-clears after copy.
  • All config stored locally — works offline, no account.

iCloud Sync

Turn on “iCloud Sync” in Settings: hosts and groups sync via a private CloudKit database; passwords and private keys sync end-to-end encrypted via the iCloud Keychain to devices on the same account.

Toggling sync requires an app restart to take effect (the container binds at launch). Secure Enclave keys are hardware-bound and do not sync.