Skip to content

GETSSH v3.0.0-preview

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 21 Oct 17:03
· 2 commits to main since this release
v3.0.0-preview
77f4ddd

中文 · English

GETSSH 3.0 预览版

3.0.0-preview · 2026-10-21

3.0 预览版提供 macOS 和 Windows 的 FUSION 版本。预览期间会继续修复问题，遇到问题请在 Issues 里告诉我们。Linux 用户请继续使用 2.0。

下载

系统 处理器 文件
macOS 13 及以上 Apple Silicon GETSSH-3.0.0-preview-arm64.dmg
macOS 13 及以上 Intel GETSSH-3.0.0-preview.dmg
Windows 10 及以上 x64 GETSSH-Setup-3.0.0-preview-x64.exe
Windows 10 及以上 ARM64 GETSSH-Setup-3.0.0-preview-arm64.exe

SHA256SUMS.txt 里是这四个文件的 SHA-256。

第一次打开：应用没有 Apple 开发者签名，Windows 安装包也没有签名。

  • macOS 13、14：在"应用程序"里右键点 GETSSH，选"打开"。
  • macOS 15 及以上：系统提示无法验证开发者以后，打开"系统设置 → 隐私与安全性"，在下方点"仍要打开"。
  • Windows：SmartScreen 提示时，点"更多信息"，再点"仍要运行"。

从 2.0 升级

  • 第一次启动时，2.0 的服务器列表自动导入主工作区。2.0 设过主密码、又没能自动打开的，会请您输入 2.0 的主密码。
  • 2.0 插件的数据复制一份到主工作区，只复制一次。已安装的插件照常加载。
  • 主机指纹、连接记录和界面设置沿用 2.0 的。
  • 2.0 的服务器文件和插件数据不改也不删，重新装回 2.0 还能用。回到 2.0 后，3.0 里新加或改过的服务器看不到；初始化脚本和代理设置会回到默认值。

数据加密存放

  • 服务器、密码、私钥、AI 会话和 AI 服务的密钥，都存在本机的加密数据库里。每个工作区一个库，用 SQLCipher 4 格式加密，钥匙各不相同。
  • 密码、私钥和口令在库里再用 AES-256-GCM 单独加密一层。界面拿不到它们，连接时由主进程直接交给 SSH。
  • 主密码是可选的，至少 12 个字符，用 Argon2id 处理，不会存下来。
    • 设了主密码，启动 GETSSH、空闲 5 分钟、锁屏或休眠以后，都要输入它。
    • 数据加上主密码，在另一台电脑上也能完整恢复。
    • 设主密码时会生成一个恢复码，只显示一次。忘了主密码时，用它找回数据。
  • 不设主密码时，钥匙由这台电脑保管：macOS 用 Secure Enclave 或钥匙串，Windows 用 TPM 或 DPAPI。这时数据只能在这台电脑上打开，换电脑要用加密备份。
  • Touch ID 和 Windows Hello 可以代替输入密码，开不开都不影响数据能否带走。
  • 可以建多个工作区。主工作区以外的工作区可以各自设密码。

加密备份

  • 选择要备份的工作区，导出成一个 .getssh-backup 文件。文件用导出密码加密：导出密码至少 12 个字符，经 Argon2id 派生出钥匙，再用 AES-256-GCM 加密。
  • 在另一台电脑上，只凭导出密码就能整份恢复，包括服务器密码和导入 GETSSH 的私钥。
  • 导出密码能打开备份里的所有工作区，包括设了单独密码的。
  • 3.0 的导入是整体替换：替换之前，会自动把当前的数据备份到旁边。

私钥存进 GETSSH

  • 可以导入 OpenSSH、PEM（PKCS#1、SEC1、PKCS#8）和 PuTTY .ppk（第 2、3 版）格式的私钥，支持 Ed25519、RSA 和 ECDSA。带口令的私钥，口令和私钥一起加密保存。
  • 可以生成新的 Ed25519 私钥，复制公钥后，加到服务器的 ~/.ssh/authorized_keys 里。
  • 服务器原来用的私钥文件，可以在连接设置里导入 GETSSH。同一个工作区里用这个文件的服务器会一起改用导入的私钥；原文件可以选择移到废纸篓（Windows 上是回收站）。
  • 不支持 DSA 私钥。
  • 还在用磁盘上私钥文件的服务器，那个文件不在加密备份里。

AI 排障

  • 可以选 OpenAI、Gemini、Claude、DeepSeek、智谱 GLM、Kimi、MiniMax、通义千问 Qwen、Ollama（本地模型）或自定义端点，使用您自己的 API 密钥。MiniMax 国内站账号、Qwen 的其他地域，在设置里填对应的服务地址。
  • 四种模式：只读问答；感知助手（读取当前终端的内容）；审批执行（每条命令经您同意才执行）；自动执行（只适合完全信任的环境）。
  • 发给模型服务之前，能识别出的敏感信息（如密码、令牌）会换成占位符。
  • 审批执行和自动执行模式下，AI 可以联网搜索，默认开启：搜索词发给公共 SearXNG 服务器、DuckDuckGo 或 Bing，只带占位符。可以在 AI 设置里关掉。
  • 过去会话的检索数据在本机生成，存在加密数据库里，不发给任何服务。

插件和 MCP

  • 插件安全模式是两种"隔离模式"时，每个后端插件在一个受系统限制的进程里运行：macOS 用 Seatbelt，Windows 用 AppContainer。插件访问文件、网络和客户端功能，要在清单里声明。"安全"模式不运行后端插件；"开发者"模式直接在主进程里运行，只适合完全信任的代码。
  • 本地 MCP 服务器也在同样的系统限制下运行。默认不能联网，也看不到您的文件，只能访问您在设置里允许的路径。
  • 插件可以用 context.secrets 加密保存令牌和密码。设置项里的密码同样加密保存。
  • 不兼容的改动：context.safeStorageEncrypt() 在 3.0 删除了，请改用 context.secrets。插件开发见 SDK 指南。

工作台

  • 潮汐引擎（Tidal Engine）：分屏、调整窗格比例、聚焦一个窗格，或者把会话移到独立窗口。
  • SFTP 在 SSH 会话旁边打开。
  • Watchdog 是一个独立进程，GETSSH 失去响应时会尝试恢复。

预览版的已知情况

  • 没有 Linux 版本。
  • macOS 应用没有 Apple 开发者签名，也没有经过公证；Windows 安装包没有签名。
  • 导入备份只能整体替换，不能合并。
  • 主机指纹、连接记录、最近连接、界面设置、插件自己存的数据和终端录像，不在加密数据库里。
  • 没有 T2 芯片的 Intel Mac 没有 Secure Enclave，没设主密码时，设备密钥存在登录钥匙串里。更新到新版本后第一次打开，macOS 可能会要求输入登录密码，允许 GETSSH 读取这个密钥，选"始终允许"即可。
  • 新版本要手动下载。可以在"设置 → 关于"里检查有没有新版本。

安装包里附带 THIRD_PARTY_NOTICES.txt，列出了用到的第三方软件和许可。MiSans 字体的许可协议原文在官网。

中文 · English

GETSSH 3.0 Preview

3.0.0-preview · 2026-10-21

The 3.0 preview is the FUSION edition for macOS and Windows. Fixes will keep coming during the preview; please report problems in Issues. On Linux, please keep using 2.0.

Downloads

System Processor File
macOS 13 or later Apple Silicon GETSSH-3.0.0-preview-arm64.dmg
macOS 13 or later Intel GETSSH-3.0.0-preview.dmg
Windows 10 or later x64 GETSSH-Setup-3.0.0-preview-x64.exe
Windows 10 or later ARM64 GETSSH-Setup-3.0.0-preview-arm64.exe

SHA256SUMS.txt lists the SHA-256 of these four files.

First launch: the app is not signed with an Apple Developer ID, and the Windows installer is not signed.

  • macOS 13 and 14: in Applications, right-click GETSSH and choose Open.
  • macOS 15 and later: after the message that the developer cannot be verified, open System Settings → Privacy & Security and click Open Anyway near the bottom.
  • Windows: when SmartScreen appears, click More info, then Run anyway.

Upgrading from 2.0

  • On first launch, the 2.0 server list is imported into the main workspace. If 2.0 had a master password that cannot be opened automatically, you are asked for it.
  • The data of 2.0 plugins is copied into the main workspace once. Installed plugins load as before.
  • Host fingerprints, connection history and interface settings carry over from 2.0.
  • The 2.0 server files and plugin data are neither changed nor deleted, so reinstalling 2.0 still works. Back on 2.0, servers added or changed in 3.0 are missing, and the init scripts and proxy settings return to their defaults.

Data is stored encrypted

  • Servers, passwords, private keys, AI sessions and the keys of AI services are kept in encrypted databases on this computer: one per workspace, in the SQLCipher 4 format, each with its own key.
  • Passwords, private keys and passphrases are encrypted once more inside the database with AES-256-GCM. The interface never receives them; when you connect, the main process hands them to SSH.
  • The master password is optional, has at least 12 characters, is processed with Argon2id and is not stored.
    • With a master password, GETSSH asks for it at launch, after 5 idle minutes, a locked screen or sleep.
    • The data and the master password are enough to restore everything on another computer.
    • Setting a master password creates a recovery code, shown only once. It opens the data if you forget the master password.
  • Without a master password, this computer keeps the keys: the Secure Enclave or the Keychain on macOS, the TPM or DPAPI on Windows. The data then opens only on this computer; use an encrypted backup to move it.
  • Touch ID and Windows Hello can replace typing a password. Whether they are on does not affect moving the data.
  • You can create several workspaces. Workspaces other than the main one can each have their own password.

Encrypted backups

  • Choose the workspaces to back up and export them to one .getssh-backup file, encrypted with an export password of at least 12 characters: Argon2id derives the key, AES-256-GCM encrypts.
  • The export password alone restores everything on another computer, server passwords and private keys stored in GETSSH included.
  • The export password opens every workspace in the backup, including those with their own password.
  • Importing in 3.0 replaces all data; the current data is backed up next to it first.

Private keys in GETSSH

  • Import private keys in OpenSSH, PEM (PKCS#1, SEC1, PKCS#8) and PuTTY .ppk (versions 2 and 3) format: Ed25519, RSA and ECDSA. A key's passphrase is stored encrypted with it.
  • Generate a new Ed25519 key and copy its public key into ~/.ssh/authorized_keys on the server.
  • A key file a server already uses can be imported from the connection settings. Servers in the same workspace that use that file switch to the imported key; you can choose to move the original file to the Trash (the Recycle Bin on Windows).
  • DSA keys are not supported.
  • A key file that a server still reads from disk is not part of encrypted backups.

AI troubleshooting

  • OpenAI, Gemini, Claude, DeepSeek, Zhipu GLM, Kimi, MiniMax, Alibaba Qwen, Ollama (local models) or a custom endpoint, with your own API key. For a MiniMax mainland China account or another Qwen region, enter that address in Settings.
  • Four modes: Read-only; Context assistant (reads the active terminal); Approval required (each command runs only after you approve it); Automatic execution (only for fully trusted environments).
  • Before a request goes to the model service, recognisable sensitive values such as passwords and tokens are replaced with placeholders.
  • In Approval required and Automatic execution, the AI can search the web (on by default): queries go to public SearXNG servers, DuckDuckGo or Bing, with the placeholders only. AI settings can turn it off.
  • Past sessions are indexed on this computer and the index is kept in the encrypted database; it is not sent to any service.

Plugins and MCP

  • In the two Isolated plugin security modes, each backend plugin runs in its own OS-confined process: Seatbelt on macOS, AppContainer on Windows. Plugins declare the files, network and client features they use in their manifest. Safe mode runs no backend plugins; Developer mode runs them in the main process and is only for fully trusted code.
  • Local MCP servers run under the same OS confinement. By default they have no network and see none of your files, only the paths you allow in Settings.
  • Plugins can store tokens and passwords encrypted with context.secrets. Password settings are stored encrypted too.
  • Breaking change: context.safeStorageEncrypt() was removed in 3.0; use context.secrets. See the SDK guide.

Workbench

  • Tidal Engine: split panes, resize them, focus one, or move a session to its own window.
  • SFTP opens next to the SSH session.
  • Watchdog, a separate process, tries to recover GETSSH when it stops responding.

Known limits of the preview

  • No Linux version.
  • The macOS app is not signed with an Apple Developer ID or notarized; the Windows installer is not signed.
  • Importing a backup replaces all data; merging is not available.
  • Host fingerprints, connection history, recent hosts, interface settings, plugins' own storage and terminal recordings are not in the encrypted databases.
  • Intel Macs without a T2 chip have no Secure Enclave, so without a master password the device key is kept in the login Keychain. The first time an updated GETSSH reads it, macOS may ask for your login password; choose Always Allow.
  • New versions are downloaded by hand. Settings → About checks for one.

The installers include THIRD_PARTY_NOTICES.txt with the third-party software and licenses used. The MiSans font license is on the website.

Assets 7
Loading