Editing Secure Shell (section)

=== Future ===

In 2023, an alternative to traditional SSH was proposed under the name SSH3<ref>{{cite web|date=2024-08-01|website=datatracker.ietf.org|title=Remote terminal over HTTP/3 connections|url=https://datatracker.ietf.org/doc/draft-michel-remote-terminal-http3}}</ref><ref>{{cite web|date=2024-02-28|website=www.ietf.org|title=Secure shell over HTTP/3 connections|url=https://www.ietf.org/archive/id/draft-michel-ssh3-00.html}}</ref><ref>{{cite arXiv|date=2023-12-12|title=Towards SSH3: how HTTP/3 improves secure shells|eprint=2312.08396 |last1=Michel |first1=François |last2=Bonaventure |first2=Olivier |class=cs.NI }}</ref> by PhD student François Michel and Professor Olivier Bonaventure and its code has been made open source.<ref>{{cite web|date=2024-07-12|website=github.com|title=ssh3|url=https://github.com/francoismichel/ssh3}}</ref> This new version implements the original SSH Connection Protocol but operates on top of [[HTTP/3]], which runs on [[QUIC]]. It offers multiple features such as:

* Faster session establishment, reducing the number of [[Round-trip delay]]s from 5-7 to 3.
* High security: while SSHv2 relies on its own protocols, SSH3 leverages [[TLS 1.3]], [[QUIC]], and [[HTTP]].
* UDP port forwarding
* X.509 certificates
* OpenID Connect

However, the name SSH3 is under discussion, and the project aims to rename itself to a more suitable name.<ref>{{cite web|date=2024-02-28|website=datatracker.ietf.org|title=Secure shell over HTTP/3 connections|url=https://datatracker.ietf.org/doc/draft-michel-ssh3/}}</ref> The discussion stems from the fact that this new implementation significantly revises the SSH protocol, suggesting it should not be called SSH3.