Skip to content
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

Suggestion: allow telnet line endings to be parameterised #148

Open
kazkansouh opened this issue Sep 19, 2020 · 1 comment
Open

Suggestion: allow telnet line endings to be parameterised #148

kazkansouh opened this issue Sep 19, 2020 · 1 comment

Comments

@kazkansouh
Copy link

Hello,

I was just using the Telnet module against a Windows server. However, currently it is hard coded to send a \n at the end of the input sequences. The server however was not accepting it and instead required a \r instead.

I have confirmed that both using the telnet command line client does this and so does Hyda. Looking at the code below it looks like this has been considered but changed for some reason:

cmd = b(val + '\n') #'\r\x00'

Taking a quick look at RFC 854 states at the end of page 11 (I haven't read it in depth, so could be mistaken):

Note that "CR LF" or "CR NUL" is required in both directions (in the default ASCII mode).

Regardless, I think it would probably make sense to allow this to be parameterised to improve compatibility with more systems?

@kazkansouh kazkansouh changed the title Suggestion: allows telnet line endings to be parameterised Suggestion: allow telnet line endings to be parameterised Sep 19, 2020
@lanjelot
Copy link
Owner

Thanks for this, can you please submit a patch? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants