Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ Suggestions
➜ Support for SSH
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Javin
(1 post) Bio
|
| Date
| Thu 26 Apr 2001 03:02 AM (UTC) |
| Message
| | Any chance of getting support for SSH? I would like to use MUSHClient as a telnet program, to telnet securely into a shell account and from there, do things in my account, and perhaps telnet from there to other MUSHes. I don't know how difficult this would be or anything... just a suggestion. | | Top |
|
| Posted by
| Nick Gammon
Australia (23,165 posts) Bio
Forum Administrator |
| Date
| Reply #1 on Thu 26 Apr 2001 03:23 AM (UTC) |
| Message
| | I think this would be a low-priority change. There are already SSH clients around (although not MUD clients), and I think that supporting other requests (like Mud Extension Protocol) would come higher up the list than that. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Buran
(5 posts) Bio
|
| Date
| Reply #2 on Thu 28 Jun 2001 02:36 AM (UTC) |
| Message
| | A bit off-topic, but the SSH client I use (very nice) is SecureCRT by VanDyke Technologies -- http://www.vandyke.com -- no complaints. When I'm on a Mac, I tend to use F-Secure, as it's the only one that does SSH1 (my main shell account doesn't have SSH2 yet) and ANSI color, which is pretty much required for tinyfugue -- sorry, Nick, I'm not on my winbox 100% of the time. :) But when I am -- I use Mushclient! | | Top |
|
| Posted by
| Guest
(1 post) Bio
|
| Date
| Reply #3 on Thu 28 Feb 2002 07:28 AM (UTC) |
| Message
| i would very much like to see the support or implementation of the ssh protocol as well. since there are more and more snoopers roaming the internet who can easily get your password and do harm, mud administrator changed the login in such a way, that you have connect to their unix machine, using a unix account, and then login in to the mud 'locally'.
redirection is another use: when a link to a mud is faster via another server/router, people login there and then connect further to the mud server.
in both cases we would all like to use the mushclient as the core client :)
just a guest
| | Top |
|
| Posted by
| Nick Gammon
Australia (23,165 posts) Bio
Forum Administrator |
| Date
| Reply #4 on Thu 28 Feb 2002 08:39 PM (UTC) |
| Message
| | This is on the suggestions list as #426 - however I have added your comments to it. :) |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Moose
(1 post) Bio
|
| Date
| Reply #5 on Mon 04 Mar 2002 12:13 AM (UTC) |
| Message
| Just so that you know, there are MU* servers already implementing SSH. FuzzballMUCK already has SSH, and last I heard ProtoMUCK may end up adding it as well. I know that FurryMUCK is the first MUCK server that has an SSH port to connect to.
I'm unsure if MUSHs/MUXs/MOOs/MUDs/etc have it added yet, mind you.
There are also two other MU* clients that have recently added SSH support (BeipMU, and Trebuchet).
Just thought that I'd let you know, as SSH has moved beyond the telnet world and into the MU* world. | | Top |
|
| Posted by
| Philip Mak
USA (35 posts) Bio
|
| Date
| Reply #6 on Tue 05 Mar 2002 09:19 AM (UTC) |
| Message
| > that you have connect to their unix machine, using a unix
> account, and then login in to the mud 'locally'.
If you have a UNIX account on the machine and they have SSH installed, you can already securely connect to the MUSH via MUSHclient, without requiring SSH support.
What you do is in your SSH client software (there's a couple decent free clients such as the one from SSH.com, PuTTY, etc.), setup port forwarding from localhost port 4201 to port 4201 on the remote host (assuming your MUSH's port is 4201). Then, set MUSHclient to connect to TCP/IP address 127.0.0.1 (that's your own computer) and port number 4201. Open the SSH connection, then you can connect using MUSHclient and it'll go through the encrypted SSH tunnel.
Of course, this will only work if you have an account on the UNIX machine to SSH into, so it's not a perfect solution. | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
26,880 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top