How to use SSL and MuckClient (Versions prior to 3.1 | Versions 3.1+ )
MuckClient upto 3.1
stunnel is a program for wrapping connections in Secure Sockets Layer encryption, just as an "https" secure web connection is the normal web protocol, HTTP , wrapped in SSL. stunnel only handles the SSL, however, so any TCP/IP socket connection--which include most Internet transfers--can be wrapped in SSL encryption. We'll be using stunnel to wrap our FurryMUCK connection in SSL.
First, you need stunnel. Stunnel.org provides Windows binaries : get the newest stable .exe, and the two DLLs--libssl32 and libeay32--from the bottom of the page. Place these files in either a dedicated "stunnel" directory (such as under "Program Files") or in your MU* client's directory. You may want to rename the .exe file "stunnel.exe" for ease--that's what I'll be calling the file.
Now we'll make a Shortcut that will run stunnel for connecting to FurryMUCK. Open the folder in which you put the stunnel.exe. Use the right mouse button to drag the stunnel.exe to the Desktop or another folder (such as one for the Start-Programs menu), and select " C reate Shortcut(s) Here." Right-click on the new Shortcut and select "P r operties." Click the "Shortcut" tab. In the " T arget" field you should see the full directory path to the stunnel.exe program; to the end of that, add:
-c -d 8899 -r muck.furry.com:8899
Click the OK button. You may at this point rename the Shortcut something like "stunnel to FurryMUCK."
When you start the Shortcut, an MS-DOS Prompt window will open and say:
2001.11.02 14:37:21 LOG5[14805619:14806723]: Using 'muck.furry.com.8899' as tcpwrapper service name
2001.11.02 14:37:23 LOG5[14805619:14806723]: stunnel 3.21a on x86-pc-mingw32-gnu WIN32
2001.11.02 14:37:23 LOG5[14805619:14806723]: FD_SETSIZE=4096, file ulimit=-1 (unlimited) - 2000 clients allowed
This means stunnel is ready to accept connections. Since we told stunnel to listen locally on port 8899, stunnel is waiting for you to connect there. So, in your MU* client, instead of connecting to muck.furry.com 8899, connect to localhost 8899. When you connect, the MS-DOS prompt will add something like:
2001.11.02 14:39:32 LOG5[14805459:14711811]: muck.furry.com.8899 connected from 127.0.0.1:2750
This means stunnel did indeed connect to FurryMUCK for you, and your MU* client is connected by a Secure Sockets Layer connection.
A final note: Your 8899 and you
So now you're running stunnel which "listens" on port 8899 for connections to forward to muck.furry.com's port 8899. There's something very important you should know about this: anyone who can connect to your computer's port 8899 will be forwarded to muck.furry.com . As far as muck.furry.com knows, you've connected again as someone else. Since wizards can see from where you connect, some MUCKs would notice this and mark you as alts of each other; if the other person caused mischief, you could be blamed.
To prevent this, you should firewall off your port 8899 from the Internet. If you have Zone Alarm , tell Zone Alarm that the stunnel.exe should not be allowed to be an Internet server.
Happy MUCKing!
Version 3.1+ directly supports SSL connections to mud/muck games which dont require a certificate!