Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2018-12-20 13:08:55
Size: 1345
Editor: Morticon
Comment:
Revision 4 as of 2018-12-23 13:41:29
Size: 3907
Editor: Morticon
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
<<TableOfContents()>>

= Introduction =
Line 3: Line 7:
For Windows, the best option is [[http://www.beipmu.com|BeipMU]]. This client is updated very frequently and the developers are extremely responsive. If you have windows 10, it is also available in the Windows Store for free. If you feel you are unable to switch to this wonderful client for whatever reason, you can use the Websocket gateway program Morticon wrote. Information is available in +read. Even if you switch to BeipMU, you may still find the gateway program useful because it can handle bad/flaky connections. The upgrade is being done because using unencrypted connections means anyone - telecom companies, coffee shops, airports, school, your neighbor, etc - can eavesdrop on what you do or say on SpinDizzy. Essentially, when you are not using an unencrypted connection, everything you type could in theory be seen by anyone. While some people claim not to be bothered by this, most would rather communications remain private. As SpinDizzy has always been on the forefront of privacy and security, this is the next logical step. We've had an SSL port long before most MUCKs supported it.
Line 5: Line 9:
For Linux, the best option is running BeipMU in WINE, or to download and manually compile the latest [[http://tinyfugue.sourceforge.net/|TinyFugue]]. It may also exist in package format for your distribution. A lot of thought went into making this decision. It was not going to move forward unless viable workarounds were provided for essentially everyone on the MUCK. With that said, the sections below detail workarounds for your specific platform(s), if your current clients do not support encryption.
Line 7: Line 11:
MacOS users can try [[http://www.riverdark.net/atlantis/|Atlantis]], though it does not appear to be updated or supported any longer. == Windows ==
Line 9: Line 13:
Phone users currently have no known clients which directly support SSL. They can either use the web client or a proxy/tunneling program that will tunnel the connection. For Windows, the best option is [[http://www.beipmu.com|BeipMU]]. This client is updated very frequently and the developers are extremely responsive. If you have windows 10, it is also available in the Windows Store for free. Just connect to port 7073 and indicate it is encrypted, and you're set.
Line 11: Line 15:
TODO: Add information about proxies and tunnels for phones and other operating systems. [[https://sourceforge.net/projects/trebuchet/|Trebuchet Tk]] also supports SSL if you install the tcltls package.

If you feel you are unable to switch to this wonderful client for whatever reason, you can use the Websocket gateway program Morticon wrote. Information is available in +read 8. It basically works like this:
  * Download the ZIP file and extract in C:\spindizzy or similar. URL is not provided here to prevent non-SD downloads.
  * Run spindizzy.bat. The command window must remain up the whole time.
  * Connect your existing muck client to 127.0.0.1 port 7072.
  * Done!

Even if you switch to BeipMU, you may still find the gateway program useful because it can handle bad/flaky connections.

If you really don't want to use the gateway program, you can try https://www.stunnel.org/ or https://nmap.org/ (for the ncat tool). With either, the configuration works like this:
  * The remote host to connect to is muck.spindizzy.org, port 7073 SSL.
  * The local port should be 7072.
  * Your MUCK client should connect to 127.0.0.1 port 7072.

For ncat in particular, this command should work:
  * ncat -l localhost 7072 --sh-exec "ncat --ssl muck.spindizzy.org 7073"

== Linux ==

Linux has multiple good options:
  * Run BeipMU in WINE
  * Download and manually compile the latest [[http://tinyfugue.sourceforge.net/|TinyFugue]]. It may also exist in package format for your distribution. Connect to port 7073 with -x to indicate encryption.
  * [[https://sourceforge.net/projects/trebuchet/|Trebuchet Tk]] also supports SSL if you install the tcltls package.

You can also use ncat and stunnel, as detailed in the Windows section.

== MacOS ==

MacOS users can try [[http://www.riverdark.net/atlantis/|Atlantis]], though it does not appear to be updated or officially supported any longer.

MacOS users may be able to use [[https://brew.sh/|Homebrew]] to install nmap (for ncat) or stunnel and then follow the Windows directions for those tools above.

== Android ==
Android users currently have no known clients in the Play store which directly support SSL. They can either use the web client or a proxy/tunneling program that will tunnel the connection. Android users can also try installing [[https://tintin.sourceforge.io/|TinTin++]] under [[https://termux.com/|Termux]]. (Use the `#ssl` command instead of `#session`.)

== iPhone ==

More information is needed on this platform.

Introduction

SpinDizzy will be moving to 100% SSL connections sometime in 2019. This means clients which do not support SSL will either need to be upgraded or a new client used. The web client always uses SSL.

The upgrade is being done because using unencrypted connections means anyone - telecom companies, coffee shops, airports, school, your neighbor, etc - can eavesdrop on what you do or say on SpinDizzy. Essentially, when you are not using an unencrypted connection, everything you type could in theory be seen by anyone. While some people claim not to be bothered by this, most would rather communications remain private. As SpinDizzy has always been on the forefront of privacy and security, this is the next logical step. We've had an SSL port long before most MUCKs supported it.

A lot of thought went into making this decision. It was not going to move forward unless viable workarounds were provided for essentially everyone on the MUCK. With that said, the sections below detail workarounds for your specific platform(s), if your current clients do not support encryption.

Windows

For Windows, the best option is BeipMU. This client is updated very frequently and the developers are extremely responsive. If you have windows 10, it is also available in the Windows Store for free. Just connect to port 7073 and indicate it is encrypted, and you're set.

Trebuchet Tk also supports SSL if you install the tcltls package.

If you feel you are unable to switch to this wonderful client for whatever reason, you can use the Websocket gateway program Morticon wrote. Information is available in +read 8. It basically works like this:

  • Download the ZIP file and extract in C:\spindizzy or similar. URL is not provided here to prevent non-SD downloads.
  • Run spindizzy.bat. The command window must remain up the whole time.
  • Connect your existing muck client to 127.0.0.1 port 7072.
  • Done!

Even if you switch to BeipMU, you may still find the gateway program useful because it can handle bad/flaky connections.

If you really don't want to use the gateway program, you can try https://www.stunnel.org/ or https://nmap.org/ (for the ncat tool). With either, the configuration works like this:

  • The remote host to connect to is muck.spindizzy.org, port 7073 SSL.
  • The local port should be 7072.
  • Your MUCK client should connect to 127.0.0.1 port 7072.

For ncat in particular, this command should work:

  • ncat -l localhost 7072 --sh-exec "ncat --ssl muck.spindizzy.org 7073"

Linux

Linux has multiple good options:

  • Run BeipMU in WINE
  • Download and manually compile the latest TinyFugue. It may also exist in package format for your distribution. Connect to port 7073 with -x to indicate encryption.

  • Trebuchet Tk also supports SSL if you install the tcltls package.

You can also use ncat and stunnel, as detailed in the Windows section.

MacOS

MacOS users can try Atlantis, though it does not appear to be updated or officially supported any longer.

MacOS users may be able to use Homebrew to install nmap (for ncat) or stunnel and then follow the Windows directions for those tools above.

Android

Android users currently have no known clients in the Play store which directly support SSL. They can either use the web client or a proxy/tunneling program that will tunnel the connection. Android users can also try installing TinTin++ under Termux. (Use the #ssl command instead of #session.)

iPhone

More information is needed on this platform.

SSL_Help (last edited 2021-06-25 19:25:30 by Jaxen)