Bug 184043 - SSH server "eats" one Hebrew character
Summary: SSH server "eats" one Hebrew character
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: openssh
Version: 4
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-05 11:17 UTC by Gregory Brodsky
Modified: 2007-11-30 22:11 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2006-03-21 18:49:07 UTC


Attachments (Terms of Use)

Description Gregory Brodsky 2006-03-05 11:17:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Description of problem:
SSH server "eats" one Hebrew character

For example, if you type A, nothing appears.
If you then type B, C - A,B appears and C does not.

(Capital chars here are purposed here to represent Hebrew chars)

Version-Release number of selected component (if applicable):
openssh-server-3.9p1-8

How reproducible:
Always

Steps to Reproduce:
1. Configure and run SSH Client with ASCII 8-bit Hebrew codepage

For example, on Linux: 

	#setLANG=he_IL
	#xterm &

	on the new window:
	#ssh 127.0.0.1

2. Type some Latin chars
3. Switch to Hebrew keyboard and type some Hebrew chars

  

Actual Results:  Last typed character is missed.

For example, if you type A, nothing appears.
If you then type B, C - A,B appears and C does not.


Expected Results:  Each typed char should appear immediately, like for Latin chars

Additional info:

I first discovered the problem with a commercial product on which I am working.  After debugging, I concluded that this is the server, not my client, problem.  I then tested it with xterm and PUTTY, and received the same result.

The same problem exists with OpenSuse10.0

Comment 1 Tomas Mraz 2006-03-06 09:48:06 UTC
Can you please verify that this still happens with latest openssh version on FC5
as soon as it is released?



Note You need to log in before you can comment on or make changes to this bug.