You are not logged in.
Hi, there!
I got an arch linux pc with openssh server. The ssh server works very well when I connect from the same machine with openssh client and putty.
But when I connect from another pc with windows 10 system, the shell behaves strangely.
Specifically, whenever I move or resize the terminal window of the ssh client, the shell behaves like I had ctrl-c keys pressed.
So I just move the terminal window in windows 10 system a little, the foreground program in the shell will recieve a SIGTERM signal, or my unfinished command line will be droped.
I tried putty for windows and bitvise ssh client, they both have the exact same problem.
Any idea how could I fix or determine the problem?
Many thanks!
Last edited by alec_alec (2016-11-08 05:13:22)
Offline
It's not a bug, it's a micro$oft feature! What if you use the Cygwin shell to ssh?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
It's not a bug, it's a micro$oft feature! What if you use the Cygwin shell to ssh?
what hind of feature is that! can i bypass it?
Offline
I just connected to my home system from this Windows 10 system using PuTTY and cannot replicate the issue. Are you using PuTTY on Windows, or did I misunderstand?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
graysky wrote:It's not a bug, it's a micro$oft feature! What if you use the Cygwin shell to ssh?
what hind of feature is that! can i bypass it?
I was being sarcastic... there are no bugs under windows, just "features"
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
I just connected to my home system from this Windows 10 system using PuTTY and cannot replicate the issue. Are you using PuTTY on Windows, or did I misunderstand?
thank you for your reply!
I was too convinced that I did something wrong with ssh server setting.
After reading your reply I started looking for problems within my windows 10 system.
As I finaly find out, this issue stops right after I kill the dictionary software in windows called PowerWord.
I guess it has something to do with the "translation-on-selection" feature of PowerWord, even through I had never switch that feature on in PowerWord's preference setting panel.
Again, thank you guys so much for helping me figure it out.
Offline
alec_alec wrote:graysky wrote:It's not a bug, it's a micro$oft feature! What if you use the Cygwin shell to ssh?
what hind of feature is that! can i bypass it?
I was being sarcastic... there are no bugs under windows, just "features"
Ssh client in cygwin isn't affected by this issue.
Ironically, I just remove the Cygwin setup in my windows system few days ago because I finished setup my linux system ...
I will keep Cygwin installed this time, for they are so reliable.
Offline
Yep. Micro$oft features ;p
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
On the subject of features: http://i.imgur.com/TQovrwC.jpg
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline