-
Notifications
You must be signed in to change notification settings - Fork 50
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
TryLoginAsync #19
Comments
You may find clarification in #5 Alternatively can you confirm the terminating character when you telnet in is the ">" expected in your specific scenario? What package/specific library are you using? |
Thanks i checked the code now and it is looking by default for ":" to be terminated with. I was looking for a general method to check against multiple telnet clients whose terminating string i do not know. |
No reason you couldn't make the calls to the log in yourself instead of using the Login wrapper that just makes two responses for terminated read calls; you could make those as generic as you like. |
Yes i am doing it that way now. |
TryLoginAsync() is returning always false
Thanks
The text was updated successfully, but these errors were encountered: