[Bug] Parse command properly in Quick Connect

[kmahyyg]

In quick connect: ssh -p 22 root@192.168.1.1 will not work. Only ssh root@192.168.1.1 -p 22 will work.

Can this command be parsed regardless of -p or other param location?

[kmahyyg]

Also, id_ed25519.pub is not correctly recognized, which will show invalid public key format in identity tab, but you're still able to proceed.

[kmahyyg]

Another Bug (or unimplemented feature): When id_rsa is encrypted with another passphrase, it will lead to directly stop the authentication since there's no way to input the passphrase.

[kmahyyg]

Another Bug: When use CJK IME without switching to English, if you are using Chinese Pinyin, then type whoami, then click enter, it should output whoami to terminal. However, it output whoamiwhoami. Something must go wrong.

[kmahyyg]

Another Bug: Delete one existing server inside Server tab will result in 5 empty servers to be added.

[kmahyyg]

Another Bug: Delete Server will not result in ServerCat to exit. There should be some cleanup mechanism.

[Lakr233]

Another Bug: Delete one existing server inside Server tab will result in 5 empty servers to be added.

Fixed

[Lakr233]

Delete Server will not result in ServerCat to exit. There should be some cleanup mechanism.

Fixed

[Lakr233]

Another Bug: When use CJK IME without switching to English, if you are using Chinese Pinyin, then type whoami, then click enter, it should output whoami to terminal. However, it output whoamiwhoami. Something must go wrong.

This should be a bug related to xterm.js, and I'm not able to fix this very soon.

[Lakr233]

Another Bug (or unimplemented feature): When id_rsa is encrypted with another passphrase, it will lead to directly stop the authentication since there's no way to input the passphrase.

The password filed is also used to decrypt the private key, I don't get it.

[Lakr233]

In quick connect: ssh -p 22 root@192.168.1.1 will not work. Only ssh root@192.168.1.1 -p 22 will work.

Can this command be parsed regardless of -p or other param location?

I did not use the argument parser, the quick connect requires -p at the end of command line so it is a to-do.

[Lakr233]

Also, id_ed25519.pub is not correctly recognized, which will show invalid public key format in identity tab, but you're still able to proceed.

Fixed

[kmahyyg]

Another Bug (or unimplemented feature): When id_rsa is encrypted with another passphrase, it will lead to directly stop the authentication since there's no way to input the passphrase.

The password filed is also used to decrypt the private key, I don't get it.

Well, This problem has two solutions:

1. Change the caption of dialog from Password to Password / SSH Private Key Passphrase. I cannot reuse my password due to security concern.
2. Implement a new dialog or new radio button to ask user if this private is encrypted (also, auto-detect would be much perfect).

---

This is my origin thinking.

$ ssh -vv username@host
debug1: Authentications that can continue: password,publickey,keyboard-interactive
debug1: Next authentication method: password
xxxxxxxxx
debug1: Next authentication method: publickey

Try the password in the dialog first, then use private key offered in the same identity, which simplified user-side configuration of identity.

So that's why I think this is a bug.

[Lakr233]

Change the caption of dialog from Password to Password / SSH Private Key Passphrase. I cannot reuse my password due to security concern.

I'll put a notice there next time.

[kmahyyg]

Thanks for your hard work. I really love this software and appreciate you work.

Another thing that lead to my attention today:

ssh to same machine but with different port (actually port forward to another machine) will lead to terminal title can not be recognized. I personally think the problem might be a race condition.

[kmahyyg]

Then, there's a bit optimization idea:

the flying-atom animation in the background image of initial tab in each new window will lead to about 40% CPU cost on my M1 MBA. It's really a lot for a SSH terminal. I hope that if a window is minimized to background, this animation should stop rendering.

[Lakr233]

the flying-atom animation in the background image of initial tab in each new window will lead to about 40% CPU cost on my M1 MBA. It's really a lot for a SSH terminal. I hope that if a window is minimized to background, this animation should stop rendering.

option will be made to disable this animation in next release
and when this view disappear it should not render any update because the timer will not connect so might be a bug on swiftui side

[kmahyyg]

Can code snippets be inserted to terminal of connected session?