1. Forum
  2. FidoNet
  3. Mystic Support

  • A39 and SSH

    From Eric Renfro@1:135/371 to All on Monday, June 04, 2018 11:16:38
    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.
    --- SBBSecho 2.27-Linux
    * Origin: Decker's Heaven -//- bbs.deckersheaven.com (1:135/371)
  • From alaorjr@gmail.com@3:770/3 to Eric Renfro on Tuesday, June 05, 2018 05:32:52
    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)
  • From Static@1:249/400 to alaorjr@gmail.com on Wednesday, June 06, 2018 00:18:27
    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

    AFAIK Netrunner doesn't support SSH. If it's trying to make a plain telnet connection to the SSH port then a handshake failure is to be expected.

    --- Mystic BBS v1.12 A39 2018/04/21 (Linux/64)
    * Origin: Subcarrier BBS (1:249/400)