Subj : Re: A39 and SSH
To   : Eric Renfro
From : alaorjr@gmail.com
Date : Tue Jun 05 2018 05:32 am

On Monday, June 4, 2018 at 12:46:58 PM UTC-3, Eric Renfro wrote:
> So, I decided to check out the latest of Mystic, got it installed on a Debian 
9
> VM, and compiled cryptlib, making it into a handy dandy little fpm-made .deb
> package, and installed everything.
>
> One of the first things I tried doing after the initial basic tests of binkp
> support was ssh.. I set the SSH port to 2222, and configured SyncTerm to
> connect on port 2222, but it just stalls out, and mis sees the connection, 
but
> never goes beyond negotiating the ssh session. In fact, the only thing I can
> seem to do once that happends is shutdown MIS and restart it because it won't
> even let go of the connection once established. Re-connecting gets hit by the
> duplicate IP so it knows something's going on.
>
> Anyone here gotten SSH working, or had similar troubles? I'm running with mis
> with setcap cap_net_bind_service=+ep, and as a regular user, not root.
>
> )))[Psi-Jack -//- Decker]
>
> ... Alimony: The ransom that the happy pay to the devil.

I have the same problem. Can anyone help?
I use netrunner over Ubuntu 18.04 and return this message:
SSH-2.0-cryptlib
,&#$@#Handshake failed

--- SoupGate-Win32 v1.05
 * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

.