Bug#708088: shellinabox: cannot input some symbols
Package: shellinabox Version: 2.14-1 Severity: normal Debian version: 8.1 Kernel version: 3.16.0-4-kirkwood #1 Debian 3.16.7-ckt11-1 (2015-05-24) armv5tel GNU/Linux Hi, I also have in Jessie (and have always had, with Lenny then Wheezy) this issue with shellinabox. I use a French keyboard, and the characters that do not work for me are: — symbol: ) FR key: ) Corresponding US key: - — symbol: ° FR key: Shift + ) Corresponding US key: - — symbol: ] FR key: AltGr + ) Corresponding US key: - — symbol: } FR key: = Corresponding US key: = — symbol: $ FR key: $ Corresponding US key: ] — symbol: £ FR key: Shift + $ Corresponding US key: ] — symbol: ¤ FR key: AltGr + $ Corresponding US key: ] — symbol: ù FR key: ù Corresponding US key: ' — symbol: % FR key: Shift + ù Corresponding US key: ' — symbol: * FR key: * Corresponding US key: # — symbol: µ FR key: Shift + * Corresponding US key: # — symbol: FR key: Corresponding US key: \ — symbol: FR key: Shift + Corresponding US key: \ — symbol: : FR key: : Corresponding US key: . — symbol: / FR key: Shift + : Corresponding US key: . — symbol: ! FR key: ! Corresponding US key: / — symbol: § FR key: Shift + ! Corresponding US key: / For some reason, though, sometimes the } becomes available... I let you imagine how frustrating it can be to interact with the shell without * ] } $ : / (thankfully, * an / work on the numeric keypad). And in a general manner, the lack of ) is also a bit distressing :-D The US key correspondence is given to give an indication about the physical location on the keyboard. For this correspondence, I used this reference: http://www.bristol.ac.uk/it-services/learning/documentation/keyboard-1/keyboard-r1-6.gif which is the QWERTY keyboard which is the closest I could find to the physical layout of a typical AZERTY keyboard. Yves. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708088: shellinabox: cannot input some symbols
Hi, Yves I believe that we have this issue solved on our unofficial fork. Please check https://github.com/shellinabox/shellinabox If I am not mistaken this issue only occurs on Firefox browser. A workaround, until fixed version is released, would be to use a different browser. Regards, Luka
Bug#708088: shellinabox: cannot input some symbols
Marc, you mean the patch from Toshihiro Sasajima, 13 May 2013 in this report? With this patch: same result! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708088: shellinabox: cannot input some symbols
Any chance you could evaluate the patch?
Bug#708088: shellinabox: cannot input some symbols
Comparable problem here, using Firefox 19.0.2 and 20.0 with german keyboard. Following keys are not working: +*#'|?\ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708088: shellinabox: cannot input some symbols
My keyboard is JP106 layout. Which is your keyboard layout? US or other? I think this problem is below. In US keyboard, @ is a same key of 2 (keyCode == 50). In JP keyboard, @ is a different key (keyCode == 64). character keycode - --- @ 64 ^ 160 - 173 : 58 ` (same key of @) ~ (same key of ^) = (same key of -) * (same key of :) In JP keyboard, asciiKey is false when press @ key. So I cannot input @. I don't see that issue with the copy I have running. @=~^`:* These appear in the login prompt for me. Could this be an issue with your web browser instead? ... I see your patch. How does this allow those characters to get through? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708088: shellinabox: cannot input some symbols
Package: shellinabox Version: 2.14-1 Severity: normal Dear Maintainer, In Login prompt of shellinabox, I pressed @ key. But I couldn't get echoback of @. I tried all keys, and I found following keys which cannot get echoback: = - ~ ^ @ ` : * . I reported this to upstream. http://code.google.com/p/shellinabox/issues/detail?id=229 -- System Information: Debian Release: 7.0 APT prefers stable APT policy: (990, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=ja_JP.eucJP, LC_CTYPE=ja_JP.eucJP (charmap=EUC-JP) Shell: /bin/sh linked to /bin/dash Versions of packages shellinabox depends on: ii adduser 3.113+nmu3 ii libc62.13-38 ii libpam0g 1.1.3-7.1 ii libssl1.0.0 1.0.1e-2 ii lsb-base 4.1+Debian8 ii zlib1g 1:1.2.7.dfsg-13 shellinabox recommends no packages. Versions of packages shellinabox suggests: ii openssl 1.0.1e-2 -- Configuration Files: /etc/shellinabox/options-available/00+Black [Errno 2] No such file or directory: u'/etc/shellinabox/options-available/00+Black' /etc/shellinabox/options-available/00_White [Errno 2] No such file or directory: u'/etc/shellinabox/options-available/00_White' /etc/shellinabox/options-available/01+Color [Errno 2] No such file or directory: u'/etc/shellinabox/options-available/01+Color' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708088: shellinabox: cannot input some symbols
I made a patch. add ascii keycode. --- a/shellinabox/vt100.js +++ b/shellinabox/vt100.js @@ -2933,8 +2933,10 @@ // } 107 var asciiKey = event.keyCode == 32 || -event.keyCode = 48 event.keyCode = 57 || -event.keyCode = 65 event.keyCode = 90; +event.keyCode == 160 || +event.keyCode == 173 || +event.keyCode = 48 event.keyCode = 58 || +event.keyCode = 64 event.keyCode = 90; var alphNumKey= asciiKey || event.keyCode == 59 ||
Bug#708088: shellinabox: cannot input some symbols
I don't see that issue with the copy I have running. @=~^`:* These appear in the login prompt for me. Could this be an issue with your web browser instead? ... I see your patch. How does this allow those characters to get through?
