I "discovered" Mystic BBS just over a week ago and I've now installed
1.12A31, which I use , for the time being, for a private BBS network for
family and close friends. Everything works flawlessly so far, and I'm truly impressed (this is my first experience with BBS software of any kind).

SSH via mis2 configuration works without a single glich after installing cryptlib. I'm wondering, though, is it possible to implement key pair certification with mis2 ssh (it ensures true Secure SHell security by eliminating the occurrence of "man in the middle" attacks.

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

I "discovered" Mystic BBS just over a week ago and I've now installed 1.12A31, which I use , for the time being, for a private BBS network for family and close friends. Everything works flawlessly so far, and I'm truly impressed (this is my first experience with BBS software of any kind).

Ola Bob, nice to see you here - and it is great to watch your improvements in Mystic matters!


 I N D R I D / C O L D 
First come smiles / Then come lies / Last is gunfire 

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Miskatonic BBS | telnet://rasppi.servebbs.org (21:1/165)

Heh, thanks Indrid! Great to be here, looking for a few answers...

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

So, it appears that Mystic mis2, during an SSH handshake, expects user: BBS
and no password, which also goes along the lines of how other BBS software
that implement ssh works. This of course is a bit weak from the standpoint of great ssh security (because no real, solid, auth key exchange takes place)
but it is a good way to implement ssh encrypted channel when privacy is preferable for the masses, easily and out of the box).
Such scheme works great with BBS-oriented programs such as SyncTERM,
netrunner and the like...

For learning purposes, I thought it would be very interesting to know how Mystic implements SSH...the inner workings, which is very likely also how
other SSH-implementing BBS do it.

So, tonight with a bit of free time on my hand, I've tried connecting to a couple of BBS's that offer SSH with native linux openSSH (from the command line), inputting user: BBS and no password, and also playing around with the following options (at one point I used them all together):

-T Don't allocate a pty
-N Don't run a remote command
-f run in background after auth
-y -y Don't perform any remote host key checking
-g allow remote host to connect to forwarded ports

I've done all this using dropbear (latest version 2016.74).

However, so far, NO JOY.

I suspect that SyncTERM and others similar BBS-oriented programs possibly directly request a subsystem (ssh -s option) and run telnet from the start along with ssh., somehow.

I would like to be able to duplicate what SyncTERM does, duplicate it with native linux openSSH from the command line...this, again, for learning purposes.

Does anyone here have any suggestions to give in this matter?

Thanks for any input,
Bob

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Correction:

My experience with BBS-oriented clients is only with SyncTERM (and now nodespy). I should not have included netrunner in the category of BBS clients capable of SSH connectivity (I don't think it is, on second thought).

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)