This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.
Yeah, unfortunately, that module does not work with newer versions of SSH. You probably just hit that limitation.
There's not a good fix for that ATM.
If you're interested in having a working method to get SSH access over the Web, you might want to pop a message in the Bug Tracker to make sure it's on Jamie's todo list.
-Eric
The fix would be to allow older protocol version logins (I think...I'm not actually sure of that...I just seem to recall that's the case). I haven't used that module in quite some time.
Jamie and I did a bit of work on a JavaScript terminal a while back, but that's still a low-priority task. Most folks who know how to use a shell already <i>have</i> a good shell, so the ssh applet gets very, very little usage.
I tried both SSH protocol 2 and 1. Neither work. In protocol 2 I get no output at all, in protocol 1 I get the same output as if I telnet to port 22 on the server.
How hard would it be to fix? I need javassh (or something like it) to give access to a DOS-style text-based application through a browser so no special software will be required on the client side. (yes, it does sound obsolete but this particular app has been developed over the last 20 years, does its job extremely well).
Yeah, unfortunately, that module does not work with newer versions of SSH. You probably just hit that limitation.
There's not a good fix for that ATM.
If you're interested in having a working method to get SSH access over the Web, you might want to pop a message in the Bug Tracker to make sure it's on Jamie's todo list.
-Eric
The fix would be to allow older protocol version logins (I think...I'm not actually sure of that...I just seem to recall that's the case). I haven't used that module in quite some time.
Jamie and I did a bit of work on a JavaScript terminal a while back, but that's still a low-priority task. Most folks who know how to use a shell already <i>have</i> a good shell, so the ssh applet gets very, very little usage.
--
Check out the forum guidelines!
I tried both SSH protocol 2 and 1. Neither work. In protocol 2 I get no output at all, in protocol 1 I get the same output as if I telnet to port 22 on the server.
How hard would it be to fix? I need javassh (or something like it) to give access to a DOS-style text-based application through a browser so no special software will be required on the client side. (yes, it does sound obsolete but this particular app has been developed over the last 20 years, does its job extremely well).