Hi,

First of all, greeting. I'm a reboot. I used to run a RA/FD based BBS in Denmark in the 90s and had long plans, to bring it back to life. As I've been using Linux for over 2 decades now, Mystic looked like a good choice. I loved RA, but I didn't want to go back to DOS.

Either way, long story short, it seems there is a problem with SSH and IPv6, when it comes to Mystic.

I'm running Mystic 1.12 A45, cryptlib3431. Cryptlib 345 was crashing Mystic
on startup, so I discarded that.

What is happening is, that if I log in using IPv4, the password gets
recognized correctly.

If I log in using IPv6, Mystic does not recognize the password and eventually blacklists me.

Has anyone seen this behavior or can replicate it ?

-M

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
* Origin: The Alien Mindbenders BBS (2:263/5)

Hello Martin!

there is a mention on the mystic wiki

There seems to be an issue with the latest CryptLib with 32-bit Linux operating

systems that will cause Mystic to crash upon startup. If you experience this problem it may be worth trying an older version that can be downloaded from the

Mystic website:

Older version: http://www.mysticbbs.com/downloads/cl3431.zip

I'm running Mystic 1.12 A45, cryptlib3431. Cryptlib 345 was crashing Mystic on startup, so I discarded that.

What is happening is, that if I log in using IPv4, the password gets recognized correctly.

If I log in using IPv6, Mystic does not recognize the password and eventually blacklists me.

Has anyone seen this behavior or can replicate it ?

did cryptlib compile ok?
syncterm also uses cryptlib

-M

Micheal


... Feel folded, spindled or mulilated, call...
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Mike's Mansion - Portland, OR - mansion.dynv6.net:2323 (1:340/201)