A while back I posted about some issues found with SyncTERM and NetRunner (alpha) getting disconnected from ENiGMA 1/2 systems when connected over SSH. I'm hoping this report will find it's way to the right authors:
It appears the issue is indeed with keepalives: When a OpenSSH style keep alive
"ping" is sent, both clients in question respond with an error packet. The keep-alive is simply a "
keepalive@openssh.com" global request which expects a reply. It has the following bytes:
// global request
80
// "
keepalive@openssh.com"
0, 0, 0, 21,
107, 101, 101, 112, 97, 108, 105, 118, 101, 64, 111, 112, 101, 110, 115,
115, 104, 46, 99, 111, 109,
// Request a reply
1
As both clients share that they use Cryptlib and I have not seen this with clients that are based on other libraries, I'm tempted to believe it's a Cryptlib issue or perhaps one must enable/handle the pings manually with cryptlib?
For now, I have disabled the keep-alives, but this has drawbacks as well: Various ISP's love to disconnect connections that are "idle" aka not respect lower level TCP/IP flags & pings usually help with this.
--- ENiGMA 1/2 v0.0.9-alpha (linux; x64; 10.13.0)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)