1. Forum
  2. fsxNet
  3. FSX MYS

  • Password Email Reset

    From niter3@21:1/199 to Avon on Thu Dec 27 10:05:52 2018
    First I installed the complied cl32.dll and also dropped in cl64.dll from CryptLib. I suggest you really should ship Mystic with these if at all possible.


    I'm using linux. I followed the Mystic Wiki guide, but Mystic will throw a runtime erorr when the libcl.so file is placed in /usr/lib.

    Any advice?

    --- Mystic BBS v1.12 A40 2018/12/24 (Linux/32)
    * Origin: Clutch BBS * telnet://bbs.clutchbbs.com (21:1/199)
  • From g00r00@21:1/108 to niter3 on Thu Dec 27 20:06:52 2018
    I'm using linux. I followed the Mystic Wiki guide, but Mystic will throw
    a runtime erorr when the libcl.so file is placed in /usr/lib.

    Are you certain you are using the proper bit level? The cryptlib you have
    must match the bit level of Mystic (32-bit Mystic = 32-bit Cryptlib)

    The only time I have seen runtime errors is when Mystic does not match the bit level of SDL2, Cryptlib, or Python. That will make it crash every time.

    --- Mystic BBS v1.12 A42 2018/12/27 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From niter3@21:1/199 to g00r00 on Fri Dec 28 08:10:28 2018
    Are you certain you are using the proper bit level? The cryptlib you
    have must match the bit level of Mystic (32-bit Mystic = 32-bit Cryptlib)

    The only time I have seen runtime errors is when Mystic does not match
    the bit level of SDL2, Cryptlib, or Python. That will make it crash
    every time.


    I'm using the kernel that shows i686 which is 32bit. I'm compiling cryptlib
    and placing it into the directory as the instructions say.

    Everything on this OS should be 32bit.

    --- Mystic BBS v1.12 A41 2018/12/27 (Linux/32)
    * Origin: Clutch BBS * telnet://bbs.clutchbbs.com (21:1/199)
  • From g00r00@21:1/108 to niter3 on Fri Dec 28 15:54:28 2018
    I'm using the kernel that shows i686 which is 32bit. I'm compiling cryptlib and placing it into the directory as the instructions say.

    Everything on this OS should be 32bit.

    Okay thanks.

    I didn't have a Linux 32-bit installation, so I spent all day today getting one downloaded and setup so I can compile and test Mystic on it.

    I can confirm I am seeing the same problem, but I don't have any more time at the moment to research the issue. I'll try to get a fix or a solution out soon. One thing I haven't tried was using an older version of Cryptlib but I have no idea if that would even work.

    I'll try to spend some time on it tonight or tomorrow. Looks like I am going to need to get an A42 our soon.

    --- Mystic BBS v1.12 A42 2018/12/28 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From g00r00@21:1/108 to niter3 on Fri Dec 28 17:35:14 2018
    I'm using the kernel that shows i686 which is 32bit. I'm compiling cryptlib and placing it into the directory as the instructions say.

    Everything on this OS should be 32bit.

    So before I jump into working on the latest Cryptlib, I compiled an older version (3.4.3) and that seems to work just fine with Mystic no crashing.

    I am wondering if the problem is with the newer Cryptlib itself on the 32-bit systems. Many Linux distributions are no longer shipping 32-bit versions so it could be they aren't actively testing with it.

    I updated the wiki.mysticbbs.com page for SSH to include a link to the 3.4.3 source code so if you want to download that and try to compile it, you may find it works for you.

    Windows seems to not have this same problem, and I have not tested Pi or
    macOS yet to see how those systems fare

    --- Mystic BBS v1.12 A42 2018/12/28 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From deon@21:2/116.1 to g00r00 on Fri Dec 28 23:23:26 2018
    On 12/28/18, g00r00 said the following...
    I am wondering if the problem is with the newer Cryptlib itself on the 32-bit systems. Many Linux distributions are no longer shipping 32-bit versions so it could be they aren't actively testing with it.

    I dont recall what the original issue is. But on a Pi, running Raspbian it is 32-bit - and I have used 3.4.3.1(? sorry whatever was originally on the wiki) and 3.4.4.1. I need to double check which one I'm using now when I get back from holidays.

    Not sure if this helps you above?

    BTW: For Debian Systems, I've made a deb out of both of them for x86_64 and armv7l.

    ...deon

    _--_|\ | Deon George
    / \ | Chinwag BBS - A BBS on a PI in Docker!
    \_.__.*/ |
    V | Coming from the 'burbs of Melbourne, Australia

    --- Mystic BBS v1.12 A39 2018/04/21 (Raspberry Pi/32)
    * Origin: Chinwag | MysticBBS in Docker on a Pi! (21:2/116.1)
  • From niter3@21:1/199 to g00r00 on Sat Dec 29 07:58:00 2018
    I updated the wiki.mysticbbs.com page for SSH to include a link to the 3.4.3 source code so if you want to download that and try to compile it, you may find it works for you.

    Windows seems to not have this same problem, and I have not tested Pi or macOS yet to see how those systems fare


    i will give this a shot as soon as i have a few mins

    --- Mystic BBS v1.12 A41 2018/12/27 (Linux/32)
    * Origin: Clutch BBS * telnet://bbs.clutchbbs.com (21:1/199)
  • From niter3@21:1/199 to g00r00 on Mon Dec 31 07:45:40 2018
    I updated the wiki.mysticbbs.com page for SSH to include a link to the 3.4.3 source code so if you want to download that and try to compile it, you may find it works for you.

    So Mystic appears to be working with this version. However, even though it
    says it was a success emailing the code out, I don't actually get the email.

    --- Mystic BBS v1.12 A41 2018/12/27 (Linux/32)
    * Origin: Clutch BBS * telnet://bbs.clutchbbs.com (21:1/199)
  • From g00r00@21:1/108 to niter3 on Mon Dec 31 14:59:40 2018
    So Mystic appears to be working with this version. However, even though
    it says it was a success emailing the code out, I don't actually get the email.

    You might want to review the node log first as the SMTP connection is logged there. But if its reporting success that should mean the server accepted the message and said it was successful... At that point its not up to Mystic anymore what happens.

    It could be that your SMTP server is refusing to relay the message for some reason or other? Or maybe it failed and Mystic is reporting a false positive but I would think it'd be more on the former issue as SMTP servers are
    probably pretty strict with sending e-mail in order to combat spam senders.

    --- Mystic BBS v1.12 A42 2018/12/31 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)