(no title)
psanford | 5 months ago
> 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.
zdw|5 months ago
bravetraveler|5 months ago
A better 'working name' would be something like sshttp3, lol. Obviously not the successor to SSH2
asveikau|5 months ago
teddyh|5 months ago
cozzyd|5 months ago
_joel|5 months ago
theandrewbailey|5 months ago
throwaway127482|5 months ago
techscruggs|5 months ago
Having SSH in the name helps developers quickly understand the problem domain it improves upon.
bingabingabinga|5 months ago
[deleted]
nine_k|5 months ago
dpflan|5 months ago
formerly_proven|5 months ago
catlifeonmars|5 months ago
pdmccormick|5 months ago
Why not just SSH/QUIC, what does the HTTP/3 layer add that QUIC doesn’t already have?
arka2147483647|5 months ago
unknown|5 months ago
[deleted]
gclawes|5 months ago
ranger_danger|5 months ago
p1mrx|5 months ago
Titan2189|5 months ago
Pronounced "Shoe"
noman-land|5 months ago
oofbey|5 months ago
zaik|5 months ago
thayne|5 months ago
Or h3s for HTTP 3 Shell?
H3rs for http3 remote shell?
ape4|5 months ago
fsckboy|5 months ago
ssh is not a shell and ssh is not a terminal, so please everybody stop suggesting name improvements that more deeply embed that confusion.
back in the day, we had actual terminals, and running inside was our shell which was sh. then there was also csh. then there was the idea of "remote" so rsh from your $SHELL would give you a remote $SHELL on another machine. rsh was not a shell, and it was not a terminal. There were a whole bunch of r- prefixed commands, it was a family, and nobody was confused, these tools were not the thing after the r-, these tools were just the r- part.
then it was realized that open protocols were too insecure so all of the r- remote tools became s- secure remote tools.
http is a network protocol that enables other things and gets updated from time to time, and it is not html or css, or javascript; so is ssh a network protocol, and as I said, not a shell and not a terminal.
just try to keep it in mind when thinking of new names for new variants.
and if somebody wants to reply that tcp/ip is actually the network protocol, that's great, more clarification is always good, just don't lose sight of the ball.
unclet|5 months ago
0x6c6f6c|5 months ago
so, maybe SSHoQ or SoQ
soq reads better for the CLI I suppose.
antod|5 months ago
manwe150|5 months ago
BobbyTables2|5 months ago
NewJazz|5 months ago
KronisLV|5 months ago
That way, when you need to use sed for editing text containing it, your pattern can be more interesting:
Wicher|5 months ago
unknown|5 months ago
[deleted]
CharlesW|5 months ago
NewJazz|5 months ago
qsh might be taken by QShell
https://en.m.wikipedia.org/wiki/Qshell
There's a whole github issue where the issue was bike shed to death.
mnsc|5 months ago
piannucci|5 months ago
guerrilla|5 months ago
nine_k|5 months ago
It's still largely SSH2, but runs on top of HTTP/3.
ok123456|5 months ago
BobbyTables2|5 months ago
e12e|5 months ago
paulryanrogers|5 months ago
unknown|5 months ago
[deleted]
akdor1154|5 months ago
diego_sandoval|5 months ago
attentive|5 months ago
moralestapia|5 months ago
Non-doers are the bottom rung of the ladder, don't ever forget that :).
literalAardvark|5 months ago