Connecting to Microsoft Azure blob (wodFtpDLX / wodFtpDLX.NET)

by dfb, Thursday, August 04, 2022, 03:07 (855 days ago) @ wodSupport

Thanks Jasmine.

Confirming we are using .Net Framework 4.8

We have been able to run a network trace when trying to connect, if this helps.

Error returned: WeOnlyDo.Exceptions.FtpDLX.ProtocolException: Could not negotiate key exchange algorithm.

(Spaces added after commas to avoid "word too long" errors)

SSH Protocol
    SSH Version 2
        Packet Length: 684
        Padding Length: 7
        Key Exchange
            Message Code: Key Exchange Init (20)
            Algorithms
                Cookie: a951aaef8388f72ad4dfc0a1148ebd0b
                kex_algorithms length: 145
                kex_algorithms string: ecdh-sha2-nistp384, ecdh-sha2-nistp256, diffie-hellman-group14-sha256, diffie-hellman-group16-sha512, diffie-hellman-group-exchange-sha256, ext-info-s
                server_host_key_algorithms length: 65
                server_host_key_algorithms string: rsa-sha2-256, rsa-sha2-512, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384
                encryption_algorithms_client_to_server length: 111
                encryption_algorithms_client_to_server string: aes128-gcm@openssh.com, aes256-gcm@openssh.com, aes128-cbc, aes192-cbc, aes256-cbc, aes128-ctr, aes192-ctr, aes256-ctr
                encryption_algorithms_server_to_client length: 111
                encryption_algorithms_server_to_client string: aes128-gcm@openssh.com, aes256-gcm@openssh.com, aes128-cbc, aes192-cbc, aes256-cbc, aes128-ctr, aes192-ctr, aes256-ctr
                mac_algorithms_client_to_server length: 87
                mac_algorithms_client_to_server string: hmac-sha2-256, hmac-sha2-512, hmac-sha2-256-etm@openssh.com, hmac-sha2-512-etm@openssh.com
                mac_algorithms_server_to_client length: 87
                mac_algorithms_server_to_client string: hmac-sha2-256, hmac-sha2-512, hmac-sha2-256-etm@openssh.com, hmac-sha2-512-etm@openssh.com
                compression_algorithms_client_to_server length: 4
                compression_algorithms_client_to_server string: none
                compression_algorithms_server_to_client length: 4
                compression_algorithms_server_to_client string: none
                languages_client_to_server length: 0
                languages_client_to_server string: [Empty]
                languages_server_to_client length: 0
                languages_server_to_client string: [Empty]
                First KEX Packet Follows: 0
                Reserved: 00000000
            Padding String: 25c2630451e8de


Many thanks.

Hi.

If you're using NET 4+, you should be able to connect using ecdh-sha2-nistp256 or ecdh-sha2-nistp384 key exchanges. Otherwise we would need to add support to match exact ones supported by azure.

Regards,
Jasmine