SSH's keystroke timing obfuscation feature sends ~100 chaff packets per keystroke to prevent timing attacks, creating significant overhead. For a high-performance multiplayer game running over SSH, this caused 50% CPU usage and doubled bandwidth consumption. The issue was resolved by forking Go's crypto library to disable

9m read timeFrom eieio.games
Post cover image
Table of contents
Why does SSH send 100 packets per keystroke?DiscoveryInvestigationRoot causeRemediationDebugging with LLMs was fun

Sort: