{"topic":{"id":14804,"title":"新奇项目推介：用 QUIC 加速 SSH: francoismichel/ssh3 软件试用","slug":"topic","userId":4668,"categoryId":4,"createdAt":"2025-06-21 11:49:49.844521","bumpedAt":"2025-06-21 11:55:03.017452","views":199,"postsCount":1,"highestPostNumber":1,"likeCount":1,"closed":false,"pinned":false,"pinnedGlobally":false,"pinnedAt":null,"pinnedUntil":null,"isBanner":false,"excerpt":"https://github.com/francoismichel/ssh3 国产用户在透过 SSH 管理国际服务器时常常被延迟搞得十分沮丧，虽然可以透过ProxyCommand /bin/nc -X 5 -x 127.0.0.1:port %h %p的方式把 SSH 的 TCP 流量包裹在其他任意协议里面，但纯 QUIC/UDP 访问远程服务器终端的方式也许有它的优点. Mosh 使用 UDP，但依赖于 OpenSSH 进行初次会话的…","deletedAt":null,"isAnonymous":false,"isPrivate":false,"isMembersOnly":false,"category":{"id":4,"name":"谈笑风生","slug":"general","color":"25AAE2"},"author":{"id":4668,"username":"IO","name":null,"avatarUrl":null},"realAuthor":{"id":4668,"username":"IO","name":null,"avatarUrl":null},"tags":[]},"posts":[{"id":57578,"postNumber":1,"raw":"https://github.com/francoismichel/ssh3\n国产用户在透过 SSH 管理国际服务器时常常被延迟搞得十分沮丧，虽然可以透过`ProxyCommand /bin/nc -X 5 -x 127.0.0.1:port %h %p`的方式把 SSH 的 TCP 流量包裹在其他任意协议里面，但纯 QUIC/UDP 访问远程服务器终端的方式也许有它的优点.\n\n[Mosh](https://mosh.org/) 使用 UDP，但依赖于 OpenSSH 进行初次会话的认证.\n本文介绍的 SSH3 可完全独立于 OpenSSH server/client使用,而且使用起来非常方便.(是否提高远程终端的反应性待观察),操作有危险,请完整阅读完[项目README](https://github.com/francoismichel/ssh3#-do-not-deploy-the-ssh3-server-on-your-production-servers-for-now)后使用.\n\n## 安装\n`go install github.com/francoismichel/ssh3/cmd/...@latest`\n\n\n## 服务器\n首次运行，生成 cert/key pair\n```\nssh3-server -generate-selfsigned-cert -url-path /XXXXXXXXXXXXX -bind 0.0.0.0:\n```\n或者若你有域名 example.com 解析到该机，也可自动获取 Let's Encrypt 的证书:\n```\nssh3-server -generate-public-cert example.com -url-path /XXXXXXXXXXXXX -bind 0.0.0.0:\n```\n\n会在当前目录下生成 `cert.pem`, `priv.key`.检视证书指纹，供后面客户端连接时参考\n```\nopenssl x509 -outform DER -in cert.pem | openssl dgst -sha256 -binary | openssl base64\n```\n\n之后仅需运行:\n```\nssh3-server -url-path /XXXXXXXXXXXXX -bind 0.0.0.0:\n```\n\n## 客户端\n\n```\nssh3 -privkey ~/.ssh/ root@:/XXXXXXXXXXXXX \n```\n\n注意这里的 SSH key 对应的是 `~/.ssh/authorized_keys` 里配置的公私钥 (而非先前服务器生成的 cert/key pair)\n\n提示你确认证书指纹是否符合，若是则将 host 保存至 `~/.ssh3/known_hosts`,之后无需再确认。","cooked":"\n国产用户在透过 SSH 管理国际服务器时常常被延迟搞得十分沮丧，虽然可以透过`ProxyCommand /bin/nc -X 5 -x 127.0.0.1:port %h %p`的方式把 SSH 的 TCP 流量包裹在其他任意协议里面，但纯 QUIC/UDP 访问远程服务器终端的方式也许有它的优点.\n

Mosh 使用 UDP，但依赖于 OpenSSH 进行初次会话的认证.
\n本文介绍的 SSH3 可完全独立于 OpenSSH server/client使用,而且使用起来非常方便.(是否提高远程终端的反应性待观察),操作有危险,请完整阅读完项目README后使用.

安装

go install github.com/francoismichel/ssh3/cmd/...@latest

服务器

首次运行，生成 cert/key pair

ssh3-server -generate-selfsigned-cert -url-path /XXXXXXXXXXXXX -bind 0.0.0.0:<port>\n

或者若你有域名 example.com 解析到该机，也可自动获取 Let's Encrypt 的证书:

ssh3-server -generate-public-cert example.com -url-path /XXXXXXXXXXXXX -bind 0.0.0.0:<port>\n

会在当前目录下生成 cert.pem, priv.key.检视证书指纹，供后面客户端连接时参考

openssl x509 -outform DER -in cert.pem | openssl dgst -sha256 -binary | openssl base64\n

之后仅需运行:

ssh3-server -url-path /XXXXXXXXXXXXX -bind 0.0.0.0:<port>\n

客户端

ssh3  -privkey ~/.ssh/<SSH key> root@<ip>:<port>/XXXXXXXXXXXXX \n

注意这里的 SSH key 对应的是 ~/.ssh/authorized_keys 里配置的公私钥 (而非先前服务器生成的 cert/key pair)

提示你确认证书指纹是否符合，若是则将 host 保存至 ~/.ssh3/known_hosts,之后无需再确认。

\n","createdAt":"2025-06-21 11:49:49.969592","updatedAt":"2025-06-21 11:55:12.492072","replyToPostNumber":null,"replyCount":0,"likeCount":1,"wordCount":365,"liked":false,"bookmarked":false,"polls":[],"reactions":[{"reaction":"🐁️","count":1,"users":[{"id":200,"username":"Srotseiticar","name":null}],"hasReacted":false},{"reaction":"❤️","count":1,"users":[{"id":200,"username":"Srotseiticar","name":null}],"hasReacted":false}],"wiki":false,"version":1,"publicVersion":1,"deletedAt":null,"foldedAt":null,"isAnonymous":false,"isOwner":false,"user":{"id":4668,"username":"IO","name":null,"avatarUrl":null,"admin":true,"moderator":false,"signatureRaw":"","signatureCooked":null}}],"hasMore":false,"lastReadPostNumber":1,"hasUrlPostNumber":false}