Mystic BBS Wiki

Mystic BBS uses Cryptlib in order to perform the encryption for SSH and SSL-based servers and clients. This library will be automatically detected on server startup, or whenever an outbound SSH menu action is executed from the BBS itself.

The following sections outline how to install Cryptlib for each particular operating system. Find your operating system in the headings below and follow the instructions (if any) to install Cryptlib. Some versions and OS combinations (for example 1.12 A48 for Windows) should simply work out of the box with no additional steps, others will require compilation and installation of Cryptlib.

Once Cryptlib is installed, most servers will have an SSL setting inside the System Configuration > Servers > Configure Servers editor. You can create new servers or enable/disable servers already created within the editor.

If you are running an OS/version that needs to compile/install Cryptlib you can find it at the following links below.

There have been some reported mixed experiences lately interchanging different versions with different operating systems and Mystic. For 64-bit Unix-based systems like Ubuntu the latest 3.4.5 release seems to be working well as reported by users. For 32-bit Unix-based systems, at least one person has said that 3.4.5 did not work and they had to use 3.4.3.1. For these reasons, several releases will be linked to below.

The latest stable version is 3.4.5 at the time of this writing and has been tested in Linux (64-bit) and ships with Windows automatically as of 1.12 A48 (SSL should work out of the box for Windows). Future version compatibility is unknown, but a link is provided to the home page for Cryptlib.

Download the versions of Cryptlib from the following links below:

Website: https://www.cs.auckland.ac.nz/~pgut001/cryptlib/download.html

Mirror of 3.4.3.1: http://www.mysticbbs.com/downloads/cl3431.zip

Mirror of 3.4.4.1: http://www.mysticbbs.com/downloads/cl3441.zip

Mirror of 3.5.0.0: http://www.mysticbbs.com/downloads/cl345.zip

In Windows, Mystic looks for the file “cl32.dll” or “cl64.dll” depending on if the 32-bit or 64-bit version of Mystic is being used. As of the 1.12 A48 release Mystic will come with these files included so you do not have to download them. However, if issues should arise you can also find these files in the links within the downloads section.

In addition to the .DLL file, Cryptlib may have a dependency on the Visual C++ runtime which may or may not need to be installed on your particular system. This depends on how the .DLL files themselves were compiled. If you have the appropriate .DLL file in the root Mystic BBS directory but you still get a message on server startup that says Cryptlib is not installed, then you likely need to install a Microsoft runtime that is required by Cryptlib (for example):

https://www.microsoft.com/en-us/download/details.aspx?id=48145

In Linux, Mystic looks for Cryptlib in the “libcl.so” file, which must be created by compiling the source code.

For many installs of Linux the compiler setup is not included by default, check by typing in a terminal:

whereis gcc

You should see several locations (like)

gcc: /usr/bin/gcc /usr/lib/gcc /usr/bin/X11/gcc /usr/share/man/man1/gcc.1.gz

If you get no locations you need to install it, using a terminal do:

sudo apt-get update
sudo apt-get install build-essential manpages-dev

Then check again with 'whereis gcc' to make sure.

The source is contained in the above download section. Once the file has been downloaded, it must be extracted into its own directory on the Linux machine. The archive has source files that are stored in the Windows format, so it must be extracted and converted to Linux format. This can be done by using the “-a” option of unzip. If this step is skipped, the source code will not properly compile.

The following steps can be executed to compile and install Cryptlib:

• Download the source code .zip into its own directory (lets say /cryptlib and cl3441.zip for this example)
• Switch to the /cryptlib directory where the cl3441.zip is located
• Type “unzip -a cl3441.zip” to extract the source code ZIP into the /cryptlib directory
• Type “sudo make shared”
• Type “ls libcl*.so*” to see the name of the generated library. For example: libcl.so.3.4.4
• Move the library into the library path and rename it so that Mystic will find it. Execute the following:
• “sudo mv libcl.so.3.4.4 /usr/lib/libcl.so”

You can now delete the /cryptlib directory if you wish. The library is installed and read to be used by Mystic!

In macOS, Mystic looks for Cryptlib in the “libcl.dylib” file, which must be created by compiling the source code.

The source is contained in the above download section. Once the file has been downloaded, it must be extracted into its own directory on the OS X machine. The archive has source files that are stored in the Windows format, so it must be extracted and converted to Unix format. This can be done by using the “-a” option of unzip. If this step is skipped, the source code will not properly compile.

The following steps can be executed to compile and install Cryptlib:

• Download the source code .zip into its own directory (lets say /cryptlib and cl3441.zip for this example)
• Switch to the /cryptlib directory where the cl3441.zip is located
• Type “unzip -a cl3441.zip” to extract the source code ZIP into the /cryptlib directory
• Type “sudo make shared”
• Type “ls libcl*.dylib*” to see the name of the generated library. For example: libcl.3.4.4.dylib
• Move the library into the library path and rename it so that Mystic will find it. Execute the following:
• “sudo mv libcl.3.4.4.dylib /usr/lib/libcl.dylib”

You can now delete the /cryptlib directory if you wish. The library is installed and read to be used by Mystic!