SSH3: Faster and rich secure shell using HTTP/3

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.

Same - this feels equivalent of some rando making a repo called "Windows 12" or "Linux 7".

LDAP2 or nextVFS... but point awarded. Feels that way because it is. Though my examples aren't great. These things just are; not really versioned. I don't know if major differences would call for ++

A better 'working name' would be something like sshttp3, lol. Obviously not the successor to SSH2

Easy: hhs instead of ssh (since the even more obvious shh is essentially impossible to google). Stands for, idk, HTTP/3 Hardened Shell or something ("host shell"? sounds like windows)

Don't use it! Create your own thing and name it however you want.

Non-doers are the bottom rung of the ladder, don't ever forget that :).

Maybe SSH/3 instead (SSH + HTTP/3)?

I like this idea!

Having SSH in the name helps developers quickly understand the problem domain it improves upon.

Yeah, that's not cool.

SSHTTP

SSH over 3: SO(3). Like the rotation group.

SSHoH

HTTPSS for more confusion

hss? Http/3 Secure Shell?

Doesn't /3 mean v3? I mean, for HTTP itself, doesn't the HTTP/3 == HTTPv3? If so, I don't see how this is any better than SSH3 - both SSH3 and SSH/3 read to me like "SSH v3"

SecureHyperTextShell (SHTS)

I meant this in jest but now that I think about it, it actually could be a decent name (?)

h3sh | hush3 | qs | qsh | shh | shh3

SSHTTP3

SSHoHTTP3

qrs for Quic Remote Shell?

Or h3s for HTTP 3 Shell?

H3rs for http3 remote shell?

Yes, but HTTP is about the only thing that versions with a slash. By writing it SSH/3, it would emphasize its relationship with HTTP/3, instead of it being the third version of SSH.

Secure Shell Hyper Text Transfer Protocol Version 3. Yikes.

How about Tortoise Shell - a little joke because its so fast

SSQ

I think it's too similar to HSTS: https://en.m.wikipedia.org/wiki/HTTP_Strict_Transport_Securi...

How about rthym or some variation?

Anything with a 3 in it is a nightmare to type quickly. shh looks like you typo'd ssh.

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.

QUICSH/T

HTTPSSH.

Why not just SSH/QUIC, what does the HTTP/3 layer add that QUIC doesn’t already have?

The ability to use HTTP authentication methods, HTTP headers, etc?

QuickShell - it should be called

No... They're one rung up from evil and dumb doers.

ussh (for udp)

SSH/HTTP/3

That way, when you need to use sed for editing text containing it, your pattern can be more interesting:

  sed 's/SSH\/HTTP\/3/SSH over HTTP\/3/g'

SSHoH3

Pronounced "Shoe"

Quicshell*

SSH over QUIC

so, maybe SSHoQ or SoQ

soq reads better for the CLI I suppose.

try:

  sed 's:SSH/HTTP/3:SSH over HTTP/3:g'

At least with GNU sed, you can use different separators so dodge the need for exscaping. | works as well.

Hyper Secure Shell (HSS)

You mean like cryptocurrency bros naming something "web 3.0"?

QSH?

remove the hyper text:

SSHTP/3 "Secure Shell Transfer Protocol Version 3"

or even:

SSHP/3 "Secure Shell Protocol Version 3"

pronounced: shoop

C.f. “JSON5”.

HTTP3 Shell or H3S

That's already a project (library for building a desktop environment).

Why not HSH, or HTTPS Shell.

HTTP under SSH, or hussh for short.

SSH2/3, maybe?

It's still largely SSH2, but runs on top of HTTP/3.

/* This is one proper bikeshedding thread if I ever saw one. */

Secure Hypertext Interactive TTY

> Doesn't /3 mean v3?

I've seen very little do that. Probably just HTTP, and it's using a slash specifically to emphasize a big change.

That sounds a bit crap

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.

Or h3ss, pronounced hess

Quissh?

HITTY then.

sshhh ... don't sidetrack the productive comment generation. (also, SSHHH as a possible name)...

How about ush then? The predecessor was rsh, and the next letter tsh is already taken

Yeah, this one. hussh is a clear winner.

ush — “You shell” — Brilliant!

At least that isn’t an existing ham radio Q-code!

RTH3EC is a certainly a mouthful…

But this SHIT is really fast!

You’ll see when the logs drop!

easy access to reverse proxies

I think you meant to say, “YAML3”

You could say it was just for SHTS and giggles?

my autism plays out also in the world of words, i.e. names of things, and my comment here is more a reply to all my surrounding comments than to yours:

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.

Quickshell/qsh?