Hacker News Reader

Why is there http/3 in the middle? SSH over QUIC makes a lot of sense and was something I thought about before.

The SSH protocol is designed to multiplex many “channels” over an encrypted tcp socket. Over each channel you can run things like a shell or SFTP.

It would need some engineering but you could keep the same SSH features but replace the multiplexing channels over tcp with QUIC channels over udp. Where does HTTP/3 fit in besides to add overhead?

View on HN

Do you want to maintain a state machine for each QUIC-SSH session 1-N pairing? Or worse, M-N pairing?

Yes. The attack surface would be much smaller.

Why not have 1:1 relationship between QUIC connection IDs and open SSH sessions?

Profiling ... of SSH sessions at QUIC level, that's why we shouldn't do 1:1 mapping between QUIC session and SSH session.

You can use HTTP for authentication.

Unless you can use an off the shelf http client to make ssh connections I can’t think of a benefit for using http headers vs non-http key value pairs.

Looks like http(s).

Which is a straight downgrade over ssh keys.

Reply on news.ycombinator.com