←back to thread

SSH3: Faster and rich secure shell using HTTP/3

(github.com)
532 points tempaccount420 | 1 comments | 27 Sep 25 14:27 UTC | HN request time: 0s | source
Show context
psanford ◴[27 Sep 25 15:48 UTC] No.45396774[source]▶
I do hate the name ssh3. I was glad to see this at the top of the repo:

> SSH3 is probably going to change its name. It is still the SSH Connection Protocol (RFC4254) running on top of HTTP/3 Extended connect, but the required changes are heavy and too distant from the philosophy of popular SSH implementations to be considered for integration. The specification draft has already been renamed ("Remote Terminals over HTTP/3"), but we need some time to come up with a nice permanent name.

replies(28): >>45396871 #>>45397296 #>>45397372 #>>45397399 #>>45397495 #>>45397597 #>>45397619 #>>45397679 #>>45397940 #>>45398115 #>>45398136 #>>45398508 #>>45398532 #>>45398631 #>>45398858 #>>45398975 #>>45399238 #>>45399719 #>>45399778 #>>45400311 #>>45400334 #>>45400419 #>>45400814 #>>45400881 #>>45401030 #>>45401354 #>>45404259 #>>45415504 #
zdw ◴[27 Sep 25 15:56 UTC] No.45396871[source]▶
Same - this feels equivalent of some rando making a repo called "Windows 12" or "Linux 7".
replies(3): >>45397120 #>>45399472 #>>45399643 #
teddyh ◴[27 Sep 25 21:51 UTC] No.45399643[source]▶
C.f. “JSON5”.
replies(2): >>45400557 #>>45401631 #
1. Dylan16807 ◴[28 Sep 25 00:14 UTC] No.45400557{3}[source]▶
Eh. JSON forfeited version numbers, and if this analogy ran all the way through then we'd be looking at a scenario where SSH is based on HTTP 1 or 2. In that situation calling the HTTP/3 version SSH3 would make a lot of sense.