@PACKAGE@ - Version @VERSION@
Packages
The various source and binary packages are available at https://www.five-ten-sg.com/@PACKAGE@/packages/.
The most recent documentation is available at https://www.five-ten-sg.com/@PACKAGE@/.
A Mercurial source
code repository for this project is available at https://hg.five-ten-sg.com/@PACKAGE@/.
A companion terminal monitor project is available at https://www.five-ten-sg.com/510ConnectbotMonitor
2019-10-04
Carl
Byington
510 Software Group
@PACKAGE@
1
@PACKAGE@ @VERSION@
@PACKAGE@
an android vt320 tn5250 terminal emulator for telnet and ssh connections
Build method
This is an android project with native code, so
"make builder style=debug" should build cleanly.
Introduction
I belive that the previous connectbot projects are improperly licensed.
They contain a mix of Apache 2.0 and GPLv2+ code, and those two licenses
are incompatible. I have relicensed this as GPLv3+, since that is
compatible with the licenses of all the sub-parts.
This fork extends previous Connectbot projects in two ways. It includes
tn5250 terminal emulation, in addition to the previous vt320 terminal
emulation. It also contains hooks for a separate monitoring process
that has access to some of the internal operations in this emulator.
Other changes from previous Connectbots
The Android SecureRandom bug has been fixed in newer versions
of Android, but this code now compensates for that bug in
older versions. If you have keys generated on older Android
devices, those keys should be discarded, and you should generate
new keys.
The underlying compression code from jcraft has
been updated. The underlying socks proxy code has
been updated. The underlying ssh code has been
updated from trilead to ganymed. Elliptic curve
crypto is now supported, but the NIST curves are
placed after the RSA and DH types in the list of
key exchange algorithms, so they should only be
used if the server does not support RSA or
DH. This change is based on on a general lack of
trust in NIST curves that have possibly been
compromised by the NSA.
The soft function keypad now has better labels, and can generate
all 24 function keys for 5250 emulation. A hardware button can
be configured to display that function keypad.
A 510Connectbot.connections text file is read (and optionally deleted) on
startup. This may be used to preconfigure the global options
and to create an initial set of host connections. This is only
useful for bulk deployments.
The font sizes are now kept with one decimal point, and font
size changes are done by scaling by a constant factor of 1.1,
rather than the linear additive 2 point factor.
On a per-host basis, you can either allow the font size to change
the number of rows and columns depending on the visibility
of the soft keyboard, or you can fix the number of rows and colums.
Using a larger font with a fixed number of rows and columns, you
may only be able to see the top left part of the logical screen that
is being used by the host system. There is no vertical or horizontal
scrolling yet.
The configurable hardware buttons can now change the font size.
The soft function keypad now includes the cursor movement keys.
Help Pages
About - including list of credits
Hints
Physical Keyboard
5250 Keys
Screen Gestures
Virtual Keyboard
Terminal Monitor
For every terminal session (local, telnet, ssh or tn5250), this
terminal emulator also makes a connection to a terminal monitor
process, which can see cursor movement and screen contents, and can
inject characters to send to the host.
The terminal monitor is invoked by calling an android Intent
named "com.five_ten_sg.connectbot.monitor.MonitorService". That
ensures that the monitor process is running, and should then
be listening on TCP port 6001 for incoming connections. The terminal
emulator then connects to the terminal monitor on port 6001.
The native android Intent and Service communication mechanisms
are not used.
The messages exchanged between the terminal emulator and the
terminal monitor are arrays of uint16 values in network byte
order. Each message starts with a uint16 message length,
followed by that many uint16 values.
The next uint16 contains the message
command value, and the remaining uint16 values are the arguments
if any for that command.
Any arguments that are characters are represented as 16 bit
unicode. Note that the first 256 such characters are identical to the
ISO-8859-1 latin character set. There is no provision for handling
surrogate pairs as in UTF-16. Keystroke arguments (see DEPRESS) are
represented as Microsoft Virtual-Key codes, defined
here.
The first message over the socket must be the INIT message
from the TE. This allows the terminal monitor to load any
required data.
That is followed by a pair of SCREENCHANGE/CURSORMOVE messages from
the TE whenever the screen contents have changed. The terminal monitor
may respond to the SCREENCHANGE message with a SCREENWATCH message to
restrict the part of the screen that is to be monitored for updates.
At any time, the terminal monitor may send GETFIELD or SETFIELD messages
to get or set the value of fields on the current screen. GETFIELD
messages from the terminal monitor must be followed by a FIELDVALUE
message from the TE.
INIT = 0 (TE -> Monitor). The argument is a string of uint16
characters. The meaning of these characters is defined by the
monitor. It might be a fully qualified path name, or some other
data used by the monitor to drive the monitoring of this
connection.
ACTIVATE = 1 (TE -> Monitor). The first argument is the
number of lines. The second argument is the number of columns.
That is followed by lines*columns uint16 character codes for
the current screen contents.
This connection is now the active connection. It is the
topmost (or only) window visible to the user - typed keystrokes
will be sent to the host on the other end of this connection.
The TE must reset the screen watch area to the entire screen.
Every ACTIVATEE message from the TE must be followed by a
CURSORMOVE message.
KEYSTATE = 2 (TE -> Monitor). The argument is a single uint16
value, 1 for key down, 0 for key up. The TE tracks a single special
key for the monitor, and reports key up/down state when it changes.
The actual key is configurable.
CURSORMOVE = 3 (TE -> Monitor).
The first argument is the line number (0..23),
the second argument is the column number (0..79), and the third
argument is the reason for sending this cursor update. REASON=0 is
from a previous CURSORREQUEST message. REASON=1 is a cursor update
related to the previous SCREENCHANGE buffer update. REASON=2 is
a cursor update caused by user keystrokes or cursor movement
triggered by SETFIELD messages from the runtime.
SCREENCHANGE = 4 (TE -> Monitor). The first argument is the
number of lines. The second argument is the number of columns.
That is followed by lines*columns uint16 character codes for
the current screen contents. The TE must reset the screen
watch area to the entire screen.
Every SCREENCHANGE message from the TE must be followed by a
CURSORMOVE message.
When the TE sends the screen contents as a result of a previous screen
watch, the screen watch area is then reset to the entire screen. The
monitor is then responsible for sending a SCREENWATCH message
to set the watch area to something appropriate for that new
screen. Once the monitor has set the watch area to some part of a
single line, there is no mechanism for the monitor to reset it to
back to the entire screen. That reset only happens when the TE sends
the screen contents.
FIELDVALUE = 5 (TE -> Monitor).
SETFIELD = 5 (Monitor -> TE).
The first argument is the line number (0..23)
and the second argument is the column number (0..79).
That is followed by the field value, a sequence of uint16
character codes from the screen buffer. The field
covers N columns, where N = (message length - 4).
When sent from the monitor to the emulator, this causes
the emulator to send the field codes to the host (for async
modes) or to set the specified field contents (for block modes).
Note that the field length may be zero, in which case the
block mode field should cleared.
If either of the line or column numbers are -1 (0xffff), the field is
taken from the current cursor position.
This is also used as the reply message from the emulator to the
monitor for a previous GETFIELD from the monitor.
GETFIELD = 6 (Monitor -> TE).
The first argument is the line number (0..23)
and the second argument is the starting column number (0..79),
and the third argument is the field length in columns.
This message causes the emulator to send a FIELDVALUE message
back to the monitor.
If either of the line or column numbers are -1
(0xffff), the block mode field is taken from the
current cursor position, the specified field length
should be ignored, and the entire field contents are
sent back in the FIELDVALUE reply message.
SCREENWATCH = 7 (Monitor -> TE).
The number of arguments must be a multiple of
three. The arguments form a sequence of triples, where
the first element is the line number (0..23), the
second element is the starting column number (0..79),
and the third element is the field length in columns
This message causes the emulator to watch the
specified parts of the screen for updates. When any of
those parts of the screen are updated by the host
(even if the old and new characters are the same) ,
the emulator will send a SCREENCHANGE message back to
the monitor. The initial screen watch area is the
entire screen. The screen watch area is reset to the
entire screen whenever the TE sends an ACTIVATE or
SCREENCHANGE message.
Subsequent screenwatch requests replace the current one, so the TE
has only one watch area at any time.
DEPRESS = 8 (Monitor -> TE). The argument is a single
uint16 value containing the vk_key value. This message
causes the emulator to simulate a keypress for that
key. This is used for the function keys and cursor
movement keys. See DEPRESSUNICODE for ascii control
characters. Note that the TE must convert these
virtual key codes into the appropriate escape sequence
used by the host protocol (VT320, 5250, 3270, etc).The
base codes are defined here.
SHOWURL = 9 (Monitor -> TE). The single argument is a sequence
of uint16 character codes forming a URL to be displayed.
Strings within the URL must be URL escaped, so all of the
characters in the argument are less than 128.
SWITCHSESSION = 10 (Monitor -> TE). There are no arguments. The TE
should display the session associated with this socket.
CURSORREQUEST = 11 (Monitor -> TE). There are no arguments. The TE
should send a CURSORMOVE update to the monitor. Cursor movement caused
by SETFIELD or DEPRESS messages does not trigger CURSORMOVE updates
in block mode (tn5250) sessions. Those messages do trigger CURSORMOVE
updates in async mode (telnet, ssh) sessions.
SAYSTRING = 12 (TE -> Monitor). The first argument is nonzero if
any current speech should be flushed. The second argument is nonzero
if this speech should be synchronous. That is followed by uint16
character codes to be spoken. Note that the language is specified
by the monitor, not the TE.
SETFOCUS = 13 (Monitor -> TE). The first argument is the
line number (-1..23) and the second argument is the column number
(-1..79). The TE should set the input focus to the specified field
position by moving the cursor.
KEYBOARD = 14 (Monitor -> TE). The argument is a single
uint16 value, 0 to hide the soft keyboard, 1 to show the soft keyboard.
DEPRESSUNICODE = 15 (Monitor -> TE). The argument is a
single uint16 value containing the unicode value. This message causes
the TE to send the keystroke to the host. This is used for ascii
control characters. Use DEPRESS for function and cursor movement
keys.
FOREGROUND = 16 (Monitor -> TE). There are no arguments.
This is sent to the TE whenever the terminal monitor may have become the
visible foreground application. The TE should now force itself to be
the visible foreground application.
TODO
The tn5250 tls key storage should use the same storage mechanism
as the base ssh key storage.
Copyright
Copyright (C) 2019-2023 by 510 Software Group <carl@five-ten-sg.com>
This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 3, or (at your option) any
later version.
You should have received a copy of the GNU General Public License along
with this program; see the file COPYING. If not, please write to the
Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.
Version
@VERSION@
2023-02-10
Carl
Byington
510 Software Group
510Connectbot.connections
5
@PACKAGE@ @VERSION@
510Connectbot.connections
connections file for @PACKAGE@
Description
The 510Connectbot.connections
sample file is below. If this file exists in the
AccuSpeech/VoiceProjects directory or in the Downloads
directory, it is read, parsed, and optionally deleted.
Comments start with # and extend to the end of the line.
The connections file is deleted unless it contains
"delete_deployment=false" in the global options
section. In that case, the file remains, and it is read
and parsed every time the app is launched.
Version
@VERSION@