SSH from Windows Terminal not working sent by Raghav Sinha 17.January 2025

[Jiří Navrátil]

Hi everybody,

I had similar problem after I started my work this year on new  version of FABRIC.

It is confusing because in Jupyter environment  the ssh from terminal  works without problems.

However, on my local VM I have got same final error as Raghav Sinha.

It is not new for me. I had this problem also in February last year but after generating new bastion_key everything was fixed.

So I repeated same procedure this year and it works fine for both platforms. Seems me it has some relation to new versions of FABRIC.

My bastion was still valid as it shows report and also examples.

One with old and one with new keys running on Jupyter term. The same experiment with Windows is different.

See more below.

Regards

Jiri Navratil at CESNET

1/==== with new bastion on Jupyter ================

fabric@winter:work-100%$ ssh -i /home/fabric/work/fabric_config/slice_key2 -F /home/fabric/work/fabric_config/ssh_config2025 rocky@2620:0:c80:1001:f816:3eff:feff:71d
Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
Warning: Permanently added ‘2620:0:c80:1001:f816:3eff:feff:71d’ (ED25519) to the list of known hosts.
Activate the web console with: systemctl enable –now cockpit.socket
Last login: Sun Jan 19 22:10:08 2025 from 2600:2701:5000:a902::c
[rocky@Node1 ~]$ exit
logout
Connection to 2620:0:c80:1001:f816:3eff:feff:71d closed.

1/==== with old bastion on Jupyter ==================

fabric@winter:work-100%$ ssh -i /home/fabric/work/fabric_config/slice_key2 -F /home/fabric/work/fabric_config/ssh_config rocky@2620:0:c80:1001:f816:3eff:feff:71d
Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
Warning: Permanently added ‘2620:0:c80:1001:f816:3eff:feff:71d’ (ED25519) to the list of known hosts.
Activate the web console with: systemctl enable –now cockpit.socket
Last login: Sun Jan 19 22:13:11 2025 from 2600:2701:5000:a902::c

[rocky@Node1 ~]$ exit
logout

2/===== from Windows with new bastion2025 in new config2025 =======

Connection to 2620:0:c80:1001:f816:3eff:feff:71d closed.
PS C:\Users\jiri\fabric_config> ssh -i .\slice_key2 -F .\fabric_ssh_config2025.txt rocky@2620:0:c80:1001:f816:3eff:feff:71d
Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
Warning: Permanently added ‘2620:0:c80:1001:f816:3eff:feff:71d’ (ED25519) to the list of known hosts.
Activate the web console with: systemctl enable –now cockpit.socket

Last login: Sun Jan 19 22:02:14 2025 from 2600:2701:5000:a902::c
[rocky@Node1 ~]$ exit
logout
Connection to 2620:0:c80:1001:f816:3eff:feff:71d closed.

2/===== from Windows with old bastion  =======

PS C:\Users\jiri\fabric_config> ssh -i .\slice_key2 -F .\fabric_ssh_config.txt rocky@2620:0:c80:1001:f816:3eff:feff:71d
Warning: Permanently added ‘bastion.fabric-testbed.net’ (ED25519) to the list of known hosts.
jiri_0000134222@bastion.fabric-testbed.net: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Connection closed by UNKNOWN port 65535

===end=====================================

[Komal Thareja]

Hi Jiri,

Could you please share the Fingerprint for your old SSH key which is not expired but not working now?

Thanks,

Komal

[Author]

Posts