http://bugs.winehq.org/show_bug.cgi?id=11621
Summary: putty.exe in telnet mode don't display anything Product: Wine Version: 0.9.55. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: fhorse@libero.it
The windows ssh/telnet application putty.exe works well in ssh mode, but in telnet mode does not display anything on the screen. I'have sniffed tcp packets and I noticed that the telnet communication works well, make login, run commands, but does not appear anything.
Sorry for my english.
http://bugs.winehq.org/show_bug.cgi?id=11621
FHorse fhorse@libero.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fhorse@libero.it
http://bugs.winehq.org/show_bug.cgi?id=11621
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://www.chiark.greenend.o | |rg.uk/~sgtatham/putty/ Keywords| |download
--- Comment #1 from Lei Zhang thestig@google.com 2008-02-19 21:51:27 --- what version of putty?
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #2 from FHorse fhorse@libero.it 2008-02-20 04:07:15 --- I'have tried 0.57, 0.58, 0.59 and 0.60 and problem is the same
http://bugs.winehq.org/show_bug.cgi?id=11621
FHorse fhorse@libero.it changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|0.9.55. |0.9.59.
http://bugs.winehq.org/show_bug.cgi?id=11621
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|0.9.59. |0.9.55.
--- Comment #3 from Lei Zhang thestig@google.com 2008-04-18 12:08:35 --- Seems to work ok here with Wine 0.9.60. I wrote a small server that prints out the data it receives on the console, ran putty, and connected to that server. Anything I typed appeared in putty and also on the server console.
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #4 from FHorse fhorse@libero.it 2008-04-23 11:29:38 --- I tried the "putty" in the "raw" mode an works well, but in telnet mode still does not work even with the version 0.9.60. You should try to enable a telnet server and connect him to recreate the problem
http://bugs.winehq.org/show_bug.cgi?id=11621
Michal Piaskowski piaskal+wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |piaskal+wine@gmail.com
--- Comment #5 from Michal Piaskowski piaskal+wine@gmail.com 2008-04-24 14:57:45 --- I can confirm this but with putty 0.6 on wine 0.9.60 + ubuntu 7.10
Putty displays everything I type but none of the data incoming from telnet server.
http://bugs.winehq.org/show_bug.cgi?id=11621
FHorse fhorse@libero.it changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|0.9.55. |1.0-rc4
http://bugs.winehq.org/show_bug.cgi?id=11621
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.0-rc4 |0.9.55.
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-09 09:52:11 --- Please don't change an originally reported version.
http://bugs.winehq.org/show_bug.cgi?id=11621
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|fhorse@libero.it |
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-09 09:53:33 --- If you are the reporter, there is no need to add yourself to the cc: list.
http://bugs.winehq.org/show_bug.cgi?id=11621
Alexandre amaciel81@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |amaciel81@gmail.com
--- Comment #8 from Alexandre amaciel81@gmail.com 2008-12-09 17:37:53 --- Hi,
I tested PuTTY in Kubuntu 8.10 64 bits and Wine 1.1.10 (responding the calling for old bugs). The result is the same: works fine in SSH mode, but don't display anything in Telnet mode.
If I can help anyway, please, contact me.
Best regards, Alexandre
http://bugs.winehq.org/show_bug.cgi?id=11621
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #9 from Austin English austinenglish@gmail.com 2008-12-09 19:58:39 --- Confirming then.
http://bugs.winehq.org/show_bug.cgi?id=11621
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source
--- Comment #10 from Austin English austinenglish@gmail.com 2009-06-08 17:14:11 --- Still present in git.
http://bugs.winehq.org/show_bug.cgi?id=11621
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de
--- Comment #11 from André H. nerv@dawncrow.de 2009-10-30 16:06:42 --- Still present in git. (tested with my winelib-putty)
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #12 from André H. nerv@dawncrow.de 2009-10-30 16:40:07 --- looks like some binary problems. the "receive"-functions gets the text(the asciis looks ok) but somehow they handle them wrong, like some controlbytes are wrong.
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #13 from André H. nerv@dawncrow.de 2009-10-31 08:38:36 --- Created an attachment (id=24473) --> (http://bugs.winehq.org/attachment.cgi?id=24473) dirty patch
after some hours in putty code i can track back the reason to wine, now i will search for a better solution than that and maybe write some tests
http://bugs.winehq.org/show_bug.cgi?id=11621
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Difficulty|--- |Hours
http://bugs.winehq.org/show_bug.cgi?id=11621
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #24473|0 |1 is obsolete| |
http://bugs.winehq.org/show_bug.cgi?id=11621
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |winsock Difficulty|Hours |---
--- Comment #14 from André H. nerv@dawncrow.de 2009-12-21 08:15:40 --- To be more clear: The Problem is about SIOCATMARK in ws2_32 There is a Testcase in ws2_32->sock->test_ioctlsocket
http://bugs.winehq.org/show_bug.cgi?id=11621
Kenneth Robinette support@securenetterm.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |support@securenetterm.com
--- Comment #15 from Kenneth Robinette support@securenetterm.com 2010-01-15 06:35:40 --- (In reply to comment #14)
To be more clear: The Problem is about SIOCATMARK in ws2_32 There is a Testcase in ws2_32->sock->test_ioctlsocket
As the author of NetTerm, SecureNetTerm, SNetTerm and SecureFTP, I am seeing the same problem with NetTerm that I see with Putty as it relates to the telnet connection problem.
Our SNetTerm product, as well as the Microsoft telnet.exe DOES NOT have this issue.
Is there been any additional information on this issue that would help us get this resolved? Where to look? Anytime we can test in the winsock area to help resolve the issue?
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #16 from André H. nerv@dawncrow.de 2010-01-15 07:54:07 --- I dont know if its a behavior of wine+linux or just linux. On Windows, if you send SIOCATMARK per ioctl it returns 1, which seems to mean "urgent data in the buffer" On Wine+Linux it returns 0 for "normal data" The best way to fix that issue is to fix it in Wine. That behavior disturbs function select_result in Putty's file ./windows/winnet.c
I already added a testcase, its the test "expected a non-zero value" in function test_ioctlsocket in file http://source.winehq.org/source//dlls/ws2_32/tests/sock.c actually line 2480
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #17 from Kenneth Robinette support@securenetterm.com 2010-01-15 09:59:00 --- (In reply to comment #16)
I dont know if its a behavior of wine+linux or just linux. On Windows, if you send SIOCATMARK per ioctl it returns 1, which seems to mean "urgent data in the buffer" On Wine+Linux it returns 0 for "normal data" The best way to fix that issue is to fix it in Wine. That behavior disturbs function select_result in Putty's file ./windows/winnet.c
I already added a testcase, its the test "expected a non-zero value" in function test_ioctlsocket in file http://source.winehq.org/source//dlls/ws2_32/tests/sock.c actually line 2480
I am not sure that this is all that is going on. Our NetTerm product DOES NOT send a SIOCATMARK, yet the behavior is much like Putty's. That is, it connects to the host ok, then about 2-3 seconds after the connect, it freezes.
Note that it IS NOT a the same place everytime. That is, if I run NetTerm without a script, I cannot type fast enough to enter my userid at the Login: prompt before the application locks up. However if I use a script, it logs in and gets to the command line then locks up.
It appears that some type of timer is involved.
The really strange thing is our SNetTerm product is not affected by the bug at all. It does a telnet connect and everything works ok. The same is true for the Microsoft telnet.exe program.
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #18 from André H. nerv@dawncrow.de 2010-01-15 10:48:49 --- Ok, looks to me like a different bug. Please open a seperate Bug for you issue, maybe with a link to a trial of your software.
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #19 from Kenneth Robinette support@securenetterm.com 2010-01-15 11:34:23 --- (In reply to comment #18)
Ok, looks to me like a different bug. Please open a seperate Bug for you issue, maybe with a link to a trial of your software.
If its alright, I like to leave it with this bug report. Lots of people associate this bug with both Putty and NetTerm and monitor for any changes.
The current version of NetTerm can be downloaded from:
http://www.securenetterm.com/pub/nt325405.exe
and includes a 60 day trial period. If more time is needed, or has been downloaded before and trial period has expired, contact me at support@securenetterm.com and I will send a new key.
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #20 from André H. nerv@dawncrow.de 2010-01-15 12:33:22 --- I just tried it and can say there is no problem using telnet with netterm. if you encounter some problems with it its definitly not the same bug as this one here and you should open a new one please.
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #21 from Kenneth Robinette support@securenetterm.com 2010-01-15 12:42:29 --- (In reply to comment #20)
I just tried it and can say there is no problem using telnet with netterm. if you encounter some problems with it its definitly not the same bug as this one here and you should open a new one please.
Are you saying you can install NetTerm and connect to a host computer telnet server with no problems? If that is correct, what version of wine are you using?
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #22 from Kenneth Robinette support@securenetterm.com 2010-01-15 14:36:03 --- (In reply to comment #21)
(In reply to comment #20)
I just tried it and can say there is no problem using telnet with netterm. if you encounter some problems with it its definitly not the same bug as this one here and you should open a new one please.
Are you saying you can install NetTerm and connect to a host computer telnet server with no problems? If that is correct, what version of wine are you using?
I found the problem. It is in the telnet tcpip network code, sort of like the Putty problem. NetTerm locks up when it issues a winsock recv()call for 1 byte with MSG_PEEK in the flags field.
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #23 from André H. nerv@dawncrow.de 2010-01-16 05:32:19 --- The NetTerm Problem is further discussed in Bug 21387, i don't want to see any new comments here regarding that issue, as its definitly not this Bug.
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #24 from Kenneth Robinette support@securenetterm.com 2010-01-16 07:51:02 --- (In reply to comment #23)
The NetTerm Problem is further discussed in Bug 21387, i don't want to see any new comments here regarding that issue, as its definitly not this Bug.
The NetTerm problem has been resolved, as reported before. Case closed!
http://bugs.winehq.org/show_bug.cgi?id=11621
--- Comment #25 from André H. nerv@dawncrow.de 2011-05-27 19:19:26 CDT --- New test: ws2_32->sock->oob_server/client
http://bugs.winehq.org/show_bug.cgi?id=11621
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mike.kaplinskiy@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=11621
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
--- Comment #26 from Bruno Jesus 00cpxxx@gmail.com 2011-08-06 20:16:48 CDT --- André, as you stated it seems like SIOCATMARK on linux always return 0 while on Windows it always returns 1 (at least in this case for Putty). The socket is marked OOBINLINE and there's a note on microsoft article http://msdn.microsoft.com/en-us/library/ms740102%28v=vs.85%29.aspx saying:
=== Note When the SO_OOBINLINE socket option is set, the SIOCATMARK IOCTL always returns TRUE, and OOB data is returned to the user as normal data. ===
If during the ioctl call we read the socket OOBINLINE flag using getsockopt we can always return 1 on wine matching the windows behavior. Or am I completely mistaken?
http://bugs.winehq.org/show_bug.cgi?id=11621
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #27 from André H. nerv@dawncrow.de 2011-09-13 12:21:02 CDT --- should be fixed by http://source.winehq.org/git/wine.git/commitdiff/fd7b94bcd2b5d8ee48f329ec370... Thx Bruno
http://bugs.winehq.org/show_bug.cgi?id=11621
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #28 from Alexandre Julliard julliard@winehq.org 2011-09-23 12:58:36 CDT --- Closing bugs fixed in 1.3.29.
http://bugs.winehq.org/show_bug.cgi?id=11621
Vitaliy Margolen vitaliy-bugzilla@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |fd7b94bcd2b5d8ee48f329ec370 | |5da9ef3fcf5ce
-
wine-bugs＠winehq.org