Earlier quoted context omitted.
Sadly, much fewer computer systems have telnet nowadays. Also, port 21 is often blocked.
23 (21 is ftp)
Yup
Why does SSH send 100 packets per keystroke?
351–360 of 375 posts
Re: Why does SSH send 100 packets per keystroke?
#352Earlier quoted context omitted.
Even if the chatbot served only as a Rubber Ducky [1], that's already valuable. I've used Claude for debugging system behavior, and I kind of agree with the author. While Claude isn't always directly helpful (hallucinations remain, or at least outdated information), it helps me 1) spell out my understanding of the system (see [1]) and 2) help me keep momentum by supplying tasks. [1] https://en.wikipedia.org/wiki/Rubb…
Rubber Ducky is a terrific name for a GPT. Also, always reminds me of Kermit singing "...you make bath time so much fun!..."
Maybe Kermit has sung it at some point, but that's Ernie's song usually
Re: Why does SSH send 100 packets per keystroke?
#353Earlier quoted context omitted.
Confusing baud and bit rates is consistent with actually being there, though.
As someone that started with 300/300 and went via 1200/75 to 9600 etc - I don't believe conflating signalling changes with bps is an indication of physical or temporal proximity.
I think it was a joke implying you'd be old enough to forget because of age, which in my case is definitely true...
Re: Why does SSH send 100 packets per keystroke?
#354Earlier quoted context omitted.
Thanks for taking the time to respond, and apologies for the contentiousness. I'm a jaded old man suffering from severe LLM fatigue, so I may have come off a bit harsh. Your write-up was a good read, and while I might be critical of your methodology, what you did clearly worked, and that's what matters in the end. Best of luck with your project, especially the go lib fork.
Eh, I was a little annoyed at the comment last night but read through the thread again today and you were clearly engaging in good faith. I totally get being exhausted at LLMs. And I don't mind the nudge to be a little less lazy and install wireshark for next time. hope I get you to play the game when it's out!
For sure. When it's out I'll give it a go.
Re: Why does SSH send 100 packets per keystroke?
#355Re: Why does SSH send 100 packets per keystroke?
#356Earlier quoted context omitted.
As someone that started with 300/300 and went via 1200/75 to 9600 etc - I don't believe conflating signalling changes with bps is an indication of physical or temporal proximity.
I think it was a joke implying you'd be old enough to forget because of age, which in my case is definitely true...
No, just that confusing the two was ubiquitous at the time 14.4k, 28k, and 56k modems were the standard.
Like it was more common than confusing Kbps and KBps.
I mean, the 3.5" floppy disk could store 1.44 MB... and by that people meant the capacity was 1,474,560 bytes = 1.44 * 1024 * 1000. Accuracy and consistency in terminology has never been particularly important to marketing and advertising, except marketing and advertising is exactly where most laypersons first learn technical terms.
Re: Why does SSH send 100 packets per keystroke?
#357Earlier quoted context omitted.
I assure you that if you rubber duck at another engineer that doesn't understand what you're doing, you will also be pummeled with information that may or may not be relevant. ;)
That isn't rubber duck debugging. It's just talking to someone about the problem. The entire point of rubber duck debugging is that the other side literally cannot respond - it's an inanimate object, or even a literal duck/animal.
Before you expand the definition to every object in the universe, maybe we could call it parrot debugging.
Re: Why does SSH send 100 packets per keystroke?
#358Earlier quoted context omitted.
Maybe Kermit has sung it at some point, but that's Ernie's song usually
Ha. Well spotted. I totally hallucinated that.
Maybe it was this one
Re: Why does SSH send 100 packets per keystroke?
#359Earlier quoted context omitted.
As someone that started with 300/300 and went via 1200/75 to 9600 etc - I don't believe conflating signalling changes with bps is an indication of physical or temporal proximity.
I think it was a joke implying you'd be old enough to forget because of age, which in my case is definitely true...
Oh, I got the implication, but I think it was such a common mistake back then, that I don't think it's age-related now - it's a bit of a trope, to assume baud and bps mean the same thing, and people tend to prefer to use a more technical term even when it's not fully understood. Hence we are where we are with terms like decimate, myriad, nubile, detox etc, forcefully redefined by common (mis)usage. I need a cup of tea, clearly.
Anyway, I didn't think my throw-away comment would engender such a large response. I guess we're not the only olds around here!
Re: Why does SSH send 100 packets per keystroke?
#3601980s: 1 packet per keystroke is too much, we must find a solution to bundle them together, for efficiency (see Nagle's algorithm, delayed ACK), also let's send everything in plaintext, including passwords 2020s: ha! with some advanced probabilistic models, we may be able to deduce something about what is being typed behind one of our layers of encryption, let's sent 100 packets per keystroke to mitigate that
Unfortunate result of the security theater.. "Someone who has access to run privileged application can run side channel attacks! Let's drop cpu performance 20 percent over the world"
As I understood it’s enough to have “access to run privileged application” anywhere where the packet goes through. So, not necessarily at client or server sides. Or did I misunderstand?