What steps will reproduce the problem?
1. From the server side, send the ASCII ENQ (5) character.
2. Shell in a Box does not send a reply to the server.
What is the expected output? What do you see instead?
When VT terminals receive an ASCII ENQ (5) character, they usually respond with
an answerback string, which is stored in the configuration of the terminal or
terminal emulator.
What version of the product are you using? On what operating system?
Version 2.10 Rev 186 on Ubuntu 10.04.4 LTS with Apache 2.2.14
Please provide any additional information below.
I work in a large institution that uses terminal emulation software capable of
returning a static answerback string when the main system sends an ASCII ENQ
(5) character to the emulator. When we install the terminal emulation software
on a PC, we set the answerback string to a value that is unique to that PC.
That way, when the main system receives the answerback, it can provide a
friendlier experience for the user. (Note that there are no security
considerations here. Although the user can change his or her own answerback
string at any time, they don't do it because they would simply be causing
themselves problems.)
We've been talking about using Shell in a Box because it's rather impressive,
but without answerback, it gets tricky for us. One thing we thought of that
could work would be for Shell in a Box to use a value provided in the URL
(e.g., https://.../shellinabox?answerback=75295) as the answerback string that
it would send back to the server upon receipt of an ASCII ENQ (5). This way,
we could place a short cut to the Shell in a Box URL for our system on each
user's PC, and custom tailor the value for the answerback parameter.
Might something like this be a possibility for Shell in a Box?
Original issue reported on code.google.com by aoneill...@gmail.com on 28 Jun 2012 at 4:43
Original issue reported on code.google.com by
aoneill...@gmail.comon 28 Jun 2012 at 4:43