Thread Net::SSH2 - LIBSSH2_ERROR_KEX_FAILURE Unable to exchange encryption keys (51 answers)
Opened by bianca at 2023-06-30 11:30

bianca
 2023-07-01 13:44
#195074 #195074
User since
2009-09-13
6986 Artikel
BenutzerIn

user image
2023-06-30T10:39:44 Linuxer
Im Skripting ist bei plink.exe gerade die Option -no-antispoof wichtig.

Ja ich nähere mich dem Ziel. Auch dir danke ich!

Frage: plink will scheinbar beim allerersten Start auf einer Kiste dies hier bestätigt haben:
Quote
The host key is not cached for this server: xyz . server . tld (port 22)
You have no guarantee that the server is the computer you think it is. The server's xyz key fingerprint is:
xyz 255 SHA256:giizgzizgizgig7zv674g75fuz
If you trust this host, enter "y" to add the key to Plink's cache and carry on connecting.
If you want to carry on connecting just once, without adding the key to the cache, enter "n".
If you do not trust this host, press Return to abandon the connection.
Store key in cache? (y/n, Return cancels connection, i for more info)

Weißt du oder jemand anderes wie man das automatisiert mit n - also einmal bestätigen - beantwortet? -N habe ich probiert und es hilft nicht.

Wenn ich -batch gebe kommt diese Meldung:
Quote
WARNING - POTENTIAL SECURITY BREACH!
The host key does not match the one Plink has cached for
this server: xyz . server . tld (port 22)
This means that either the server administrator has changed the host key, or you have actually connected to another computer pretending to be the server.
The new xyz key fingerprint is: xyz 255 SHA256:ihvihvuvugv6556gvzu
Connection abandoned.
FATAL ERROR: Cannot confirm a host key in batch mode
10 print "Hallo"
20 goto 10

View full thread Net::SSH2 - LIBSSH2_ERROR_KEX_FAILURE Unable to exchange encryption keys