mridgers / clink

Bash's powerful command line editing in cmd.exe
mridgers.github.io/clink
GNU General Public License v3.0
3.22k stars 283 forks source link

Cannot ssh since last update/restart #590

Closed mboeker closed 1 month ago

mboeker commented 1 month ago

I don't know if this is a tabby issue or a clink issue, I'm creating it in both.

My .ssh/config:

Host *
  IdentityFile ~/.ssh/id_rsa
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  ServerAliveInterval 300
  TCPKeepAlive yes

This worked fine before the last time I rebooted my laptop. It also still works fine in Putty:

Using username "mboeker".
Authenticating with public key "imported-openssh-key"
Welcome to Ubuntu 14.04 LTS (GNU/Linux 3.13.0-170-generic x86_64)

However in Tabby it is no longer working:

C:\Users\mboeker>ssh sbg-saio
Warning: Permanently added '10.220.24.117' (ED25519) to the list of known hosts.
mboeker@10.220.24.117's password:

Both of those sessions go to the same system using the same key and ssh config.

mboeker commented 1 month ago

So it seems mobaxterm can still ssh, but visual code cannot, so this is not an issue with only tabby/clink

chrisant996 commented 1 month ago

You opened this issue in an abandoned repo.

Consider upgrading to Clink v1.7.3 at https://github.com/chrisant996/clink.

Also, it's very unlikely the problem has anything to do with Clink.

mboeker commented 1 month ago

Thanks for the info! And yes it turns out it was unrelated to clink.

Sincerely | Mit freundlichen Grüßen

Martin Ananda Boeker Uptime Solution GmbH

On Wed, Oct 23, 2024, 14:57 Chris Antos @.***> wrote:

You opened this issue in an abandoned repo.

Consider upgrading to Clink v1.7.3 at https://github.com/chrisant996/clink .

Also, it's very unlikely the problem has anything to do with Clink.

— Reply to this email directly, view it on GitHub https://github.com/mridgers/clink/issues/590#issuecomment-2432066110, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE3BVJ5UR2TBGZSSOH3YVXTZ46MJXAVCNFSM6AAAAABQOFHUAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZSGA3DMMJRGA . You are receiving this because you authored the thread.Message ID: @.***>