TCP Selective Ack is very much a thing, but it does take extra memory so lots of TCP stacks exclude it or disable it by default.
TCP Selective Ack is very much a thing, but it does take extra memory so lots of TCP stacks exclude it or disable it by default.
TCP was never designed with wifi in mind. TCP retransmission was only ever meant to handle drops due to congestion, not lossy links.
Tmux is a wonderful complement to mosh. Together you get persistence even when your local client loses power (speaking from experience)
I worked with mosh for years to connect to servers on other continents. It was impossible to work otherwise. It only has two small warts: forwarding, and jump hosts.
The second is fixable/ish with an overlay network, but that isn’t always an option if you don’t control the network. I tried to solve this with socat but wasn’t able to configure it correctly - something about the socket reuse flag was very unhappy.
Also that in order to exploit this it requires an active man in the middle. Which requires any of the following:
Almost all of those have decent mitigations like 801.x and BGP monitoring. The best mitigation is that you can just change your client config to disable those ciphersuites though.
I’m very ok with leaving that behind. It was pompous and unhelpful. But you can pry the puns from my cold dead hands!
What’s the Lore of this picture? And why is the Hugh of his skin…off?
Holy propaganda batman!
The list of articles on that website is…extremely focused on one subject only.