-
Notifications
You must be signed in to change notification settings - Fork 638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PUTTY broken on snapshot builds #2563
Comments
I'm sorry to say it is still broken.
|
iirc PuTTY should be in RAW socket and not telnet to avoid a bunch of assumptions it makes about the data. Plus, Terminal > Implicit cr in every lf would make output much nicer. |
|
|
So, settings I mentioned above are enough? |
See #2562
(and possibly any other 'interactive' client that splits data packets like PUTTY does)
Server processing ignores special TELNET newlines sent by PUTTY (fixed in PUTTY config, though)
Server processing ignores packets without newlines (either
\r\n
or\n
)espurna/code/espurna/telnet.cpp
Lines 538 to 540 in 988a972
espurna/code/espurna/telnet.cpp
Lines 569 to 574 in 988a972
We get two packets instead of one, like with nmap-nc or busybox implementation
I see no option in putty to not do this kind of stuff, but it is possible there is something
Algorithm above could either feed internal parser repeatedly, or keep our pbufs for some amount of time and repeat parsing line-like data once more... data is available
Server also always sends
\n
, but this is mostly a config issue (implicit CR after LF)The text was updated successfully, but these errors were encountered: