> And ssh tunneling web traffic looks quite different from normal ssh usage anyways.
Could you explain this further, this seems counter to my understanding of encrypted traffic!
Could you explain this further, this seems counter to my understanding of encrypted traffic!
Active web browsing requires downloading a crapton of files with wildly different sizes and sporadic timings between them. Add normal user interaction, API requests, ad cycles, long video streams that won't max out all bandwidth, all happening at once across multiple tabs. The client also sends much more data with each TLS handshake and all those HTTP headers.
This could probably be masked by deliberately filling idle periods with garbage data just to appear as a stable data stream both ways.
Not much good for images or video, but you could easily read https://text.npr.org/