SSH: Cursor sometimes on wrong line after exiting editors etc.

Hello,

Are you using the Rebex SSH shell or the native SSH shell?

Regards,

Native, I think (listed as "Telnet, SSH, RAW, rLogin").

Thanks for the fast reply.

We'll look into this issue, thanks for reporting it.

Regards,

Hello,

Could you try the "SSH Shell" session type rather than the "SSH Shell (Rebex)" or the "Telnet, SSH, RAW, rLogin" types? The latter two are pretty much the same, it uses a third party control for the terminal. The "SSH Shell" type uses our own integration based on PuTTY.

Regards,

Hi Hubert,

Sorry for not replying earlier, I've been too busy.
I don't see "SSH Shell" among the connection types, is that a plug-in?

This is what I get (I can't promise that the screenshot will remain up there for long):

Hello Luc,

What version of RDM are you running?

If you are running the Free Edition, could you try the latest version - http://remotedesktopmanager.com/Home/Download

Best regards,

Enterprise 10.6.7.0

Hi Luc,

In this case, could you try the latest beta (10.9.13.0) - http://remotedesktopmanager.com/Home/Download#beta

The session that you are looking for is present in that version.

Best regards,

Hi,
Sorry for the delay, but I decided to wait for a non-beta release with this session type because it wasn't that important.
I got that now, but there's something else not quite going as it should with it.

I created a new session to test it, using the internal SSH client with the same host and username as a working "Putty (Telnet, SSH, RAW, rLogin)" session definition. Set it to use "My private SSH key" just like that session too.

In version 11.0.0.0, it didn't work: the connection was never established. It seemed to start connecting, but just quit and returned to the dashboard before the terminal window (tab) was visible. No error messages or anything.
In version 11.0.1.0 it works, but it always prompts for my personal key passphrase, even though there is no passphrase set on it. When I click cancel on that prompt, it continues to connect and succeeds.
That prompt does NOT appear with the original session, yet it is using the same private key.

I received version 11.0.2.0 today.
Still prompts for the private key passphrase (which it shouldn't, there isn't one configured), and then continues successfully when I cancel out of that dialog.

Now I also noticed that when Putty Agent (Pageant) is running, RDM prompts for my personal key passphrase, but the connection is authenticated using the key from Agent.
Start of console output in the session:
Using username "root".
Authenticating with public key "rsa-key-20120511" from agent
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-63-generic x86_64)

When Pageant is not running, authentication is done with the copy of my personal key stored in RDM, with this output:
Using username "root".
Authenticating with public key "rsa-key-20120511"
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-63-generic x86_64)

Hello Luc,

Since our terminal is based on PuTTY, we allow the same features as PuTTY, which includes working with its agent. This feature will be disabled in the next version of RDM since the two features can contradict as you've mentionned (RDM prompting, but connecting using the agent which doesn't prompt).

As for the passphrase prompting when it shouldn't, I'll take a look at this and get back to you. Just to confirm, this is using the new SSH Shell type and not the SSH Shell (Rebex) type, right?

Regards,

Hi Hubert,
That's correct, I was trying out the new SSH Shell type.
It doesn't prompt when the same key is used with Rebex.

Hello Luc,

I think I found what the issue is. When saving the SSH Shell connection, the "prompt for password" checkbox was checked as you chose "My personal private key" option, and it still saved. This is a bug and it will be fixed in the next version of RDM.

You can fix the current connection(s) with this command that you can run by selecting the entries you want to change > right click > edit > batch edit > batch action > custom powershell command:
$connection.Terminal.PrivateKeyPromptForPassPhrase = $FALSE;
$RDM.Save();This will forcibly remove the private key passphrase prompt from the selected connections. You can do the opposite by substituting "$FALSE" for "$TRUE". Could you tell me if this fixes your issue? It seems to be the only way I can reproduce that prompt.

Regards,

Hi Hubert,
That worked.

I had first tried to make the 'prompt for password' checkmark go away in the connection properties / private key tab, but it remained checked and grayed out.
Selecting 'no private key', saving, and then selecting the key again didn't solve it.

Hello Luc,

Thanks for trying this method, I'm glad this works. As I said, it shouldn't happen in the upcoming version of RDM so if you encounter this issue again, be sure to tell us.

Regards,