[Fli4l_dev] Update per SSH geht nicht, command-line scp/sftp client funktioniert nicht mehr

[Friedhold Schuster]

jetzt:

Am 03.01.2020 um 17:36 schrieb Gotthard Anger:
> Noe, irgendwo hast Du Dich vertippt,
> bei mir sieht das so aus:

E:\Fli4l-Neu-2018\Tarball\fli4l-4.0.0-r57498-testing>cmd.exe
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

E:\Fli4l-Neu-2018\Tarball\fli4l-4.0.0-r57498-testing>windows\plink.exe 
-v fli4l@
172.18.2.99
Looking up host "172.18.2.99" for SSH connection
Connecting to 172.18.2.99 port 22
We claim version: SSH-2.0-PuTTY_Release_0.73
Remote version: SSH-2.0-dropbear_2018.76
Using SSH protocol version 2
No GSSAPI security context available
Doing ECDH key exchange with curve Curve25519 and hash SHA-256 
(unaccelerated)
Server also has ecdsa-sha2-nistp521/ssh-dss host keys, but we don't know 
any of
them
Host key fingerprint is:
ssh-rsa 2063 21:18:75:28:00:26:0d:d0:fd:bf:ab:9d:dc:7d:72:5e
Initialised AES-256 SDCTR (AES-NI accelerated) outbound encryption
Initialised HMAC-SHA-256 (unaccelerated) outbound MAC algorithm
Initialised AES-256 SDCTR (AES-NI accelerated) inbound encryption
Initialised HMAC-SHA-256 (unaccelerated) inbound MAC algorithm
Using username "fli4l".
fli4l at 172.18.2.99's password:

so richtig?

Dankeschön