๐Ÿš€ Exciting news from Belgium๐Ÿ‡ง๐Ÿ‡ช! 4 days ago, a team of researchers has published a paper on a new implementation of SSH over HTTP/3.

๐Ÿ“„ Discover their findings and dive into the technical details here: https://arxiv.org/abs/2312.08396

Find the Go implementation at: https://github.com/francoismichel/ssh3

For all your technical questions the author's emails are in the PDF or directly to @obonaventure , you could also open a Github issue at: https://github.com/francoismichel/ssh3/issues

#SSH #HTTP #Cybersecurity #Innovation #BelgianTech

Towards SSH3: how HTTP/3 improves secure shells

The SSH protocol was designed in the late nineties to cope with the security problems of the telnetf family of protocols. It brought authentication and confidentiality to remote access protocols and is now widely used. Almost 30 years after the initial design, we revisit SSH in the light of recent protocols including QUIC, TLS 1.3 and HTTP/3. We propose, implement and evaluate SSH3, a protocol that provides an enhanced feature set without compromise compared to SSHv2. SSH3 leverages HTTP-based authorization mechanisms to enable new authentication methods in addition to the classical password-based and private/public key pair authentications. SSH3 users can now configure their remote server to be accessed through the identity provider of their organization or using their Google or Github account. Relying on HTTP/3 and the QUIC protocol, SSH3 offers UDP port forwarding in addition to regular TCP forwarding as well as a faster and secure session establishment. We implement SSH3 over quic-go and evaluate its performance.

arXiv.org
@Pol
Binding host keys to x509 and the CAs seems like a step backwards instead of having local CA/PKI bound to hardware.
@Foxboron @Pol This is a prototype, this is not the focus of this piece of software
@raito @Pol
"Prototype" isn't mentioned once in the readme.
It says experimental and even then it makes security claims about the SSH PKI model.
@Foxboron @Pol Right, we can criticize them for not taking the time to write it in their README, I surmise they spend quite the time on the rest and on the paper which contains 8 references of the word prototype. :)
@raito @Pol
Can't hide behind "prototype" in the academic paper if your entire README is a product pitch to replace ssh :p

@Foxboron @Pol Well, who never write a marketing cheesy README in anticipation with higher ambition than what the actual project was. :)

I would give them some rest and wait for the dust to settle before going at them relentlessly, weighting every word they use :P.

@Foxboron @Pol But it already replaced SSH for me in almost all of my infrastructure ;)