[jira] [Commented] (NET-549) Telnet does not convert LF to CRLF in ASCII mode

["Sebb (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NET-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080110#comment-14080110 ] 

Sebb commented on NET-549:
--------------------------

I can confirm the problem when using the TelnetClientExample on MacOS.

It looks like the fix for NET-387 caused the issue.

It looks like what is needed is a combination of the original and new behaviour.
i.e. for binary connections the new behaviour is needed, and for ASCII, the old behaviour, which converts LF to CRLF.

Fix applied:

URL: http://svn.apache.org/r1614785
Log:
NET-549 - Telnet does not convert LF to CRLF in ASCII mode

Modified:
    commons/proper/net/trunk/src/changes/changes.xml
    commons/proper/net/trunk/src/main/java/org/apache/commons/net/telnet/TelnetOutputStream.java

If you want to try the latest automated snapshot build (no guarantees), it can be found at

https://repository.apache.org/content/repositories/snapshots/commons-net/commons-net/3.4-SNAPSHOT/

Build ids from 20140730.224154-1 contain the fix.

> Telnet does not convert LF to CRLF in ASCII mode
> ------------------------------------------------
>
>                 Key: NET-549
>                 URL: https://issues.apache.org/jira/browse/NET-549
>             Project: Commons Net
>          Issue Type: Bug
>          Components: Telnet
>    Affects Versions: 3.3
>         Environment: Windows 7, Java 1.7.
>            Reporter: Pradeep Natarajan
>              Labels: 2.2, 3.3.0, telnet, windows
>             Fix For: 3.4
>
>
> Hi,
> We are using your library to connect/login to some Windows and Foundary devices via Telnet.
> The source(client) is a Windows 7 professional windows machine and all the servers we are trying to connect are Windows machines running Microsoft(R) Windows(R) Server 2003, Standard Edition.
> In version 2.2 we were able to connect and then login successfully to these devices with no issues.
> However, on upgrade to 3.3 version, we are unable to login to these devices successfully.
> In v 3.3, after entering the username and hitting enter, there is no response at all. However in v 2.2, as soon as you enter the username and hit enter, password prompt comes back for us to enter the password and we are logged in successfully. 
> I compraed the packet captures between the two versions for the same target server machine. The only difference I can see is when the user name is set, in v2.2 a '\r' is appended to the end of the username where is v 3.3, this '\r' is missing. Is this due to any change in library?
> I can provide the packet capture/logs if required. Please let us know if this is a known issue or if there are any workarounds. 
> Thanks
> -Pradeep



--
This message was sent by Atlassian JIRA
(v6.2#6252)