Why does SSH send 100 packets per keystroke?
21–30 of 375 posts
Re: Why does SSH send 100 packets per keystroke?
#22> Keystroke obfuscation can be disabled client-side. please never do that (in production) if anyone half way serious tries they _will_ be able to break you encryption end find what you typed this isn't a hypothetical niche case obfuscation mechanism, it's a people broke SSH then a fix was found case. I don't even know why you can disable it tbh.
Re: Why does SSH send 100 packets per keystroke?
#23> That 20ms is a smoking gun - it lines up perfectly with the mysterious pattern we saw earlier! Speaking of smoking guns, anybody else reckon Claude overuses that term a lot? Seems anytime I give it some debugging question, it'll claim some random thing like a version number or whatever, is a "smoking gun"
smoking gun, you're absolutely right, good question, em dash, "it isn't just foo, it's also bar", real honest truth, brutal truth, underscores the issue, delves into, more em dashes, . It's nauseating.
Considering what these LLMs bring to the table, I think a little tolerance for their cringe phrases is in order.
Re: Why does SSH send 100 packets per keystroke?
#24> I am working on a high-performance game that runs over ssh. WAT. Please no.
Re: Why does SSH send 100 packets per keystroke?
#25Found your problem.
But it is an interesting world where you can casually burrow into a crypto library and disable important security features more easily than selecting the right network layer solution.
Re: Why does SSH send 100 packets per keystroke?
#26> That 20ms is a smoking gun - it lines up perfectly with the mysterious pattern we saw earlier! Speaking of smoking guns, anybody else reckon Claude overuses that term a lot? Seems anytime I give it some debugging question, it'll claim some random thing like a version number or whatever, is a "smoking gun"
ChatGPT too. And "lines up perfectly" when it doesnt actually line up with anything
Re: Why does SSH send 100 packets per keystroke?
#27> That 20ms is a smoking gun - it lines up perfectly with the mysterious pattern we saw earlier! Speaking of smoking guns, anybody else reckon Claude overuses that term a lot? Seems anytime I give it some debugging question, it'll claim some random thing like a version number or whatever, is a "smoking gun"
Re: Why does SSH send 100 packets per keystroke?
#28> Keystroke obfuscation can be disabled client-side. please never do that (in production) if anyone half way serious tries they _will_ be able to break you encryption end find what you typed this isn't a hypothetical niche case obfuscation mechanism, it's a people broke SSH then a fix was found case. I don't even know why you can disable it tbh.
Re: Why does SSH send 100 packets per keystroke?
#29Earlier quoted context omitted.
ChatGPT too. And "lines up perfectly" when it doesnt actually line up with anything
"You're so right, that nice catch lines up perfectly!"
Re: Why does SSH send 100 packets per keystroke?
#30> That 20ms is a smoking gun - it lines up perfectly with the mysterious pattern we saw earlier! Speaking of smoking guns, anybody else reckon Claude overuses that term a lot? Seems anytime I give it some debugging question, it'll claim some random thing like a version number or whatever, is a "smoking gun"
Yes! While this post was written entirely by me, I wouldn't be surprised if I had "smoking gun" ready to go because I spent so much time debugging with Claude last night.