rsa-sha2-256, rsa-sha2-512, x509v3-rsa2048-sha256

ssh-dss

Security Status: Insecure because of the inherit weakness (key length is limited to 1024 bits).Status in SmartFTP: Only offered for compatibility with legacy servers. It will be removed in the near future.

ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521

Security Status: Secure with some concerns.Status in SmartFTP: Offered.

ssh-ed25519

Security Status: Secure.Status in SmartFTP: Offered and the preferred algorithm.

Key Exchange Algorithms

curve25519-sha256

Security Status: Secure.Status in SmartFTP: Offered and the preferred algorithm.

ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521

Security Status: Secure with some concerns.Status in SmartFTP: Offered.

diffie-hellman-group-exchange-sha1, diffie-hellman-group14-sha1

Security Status: DH groups with a group size equal or greater than 2048-bit are secure. But the SHA1 signature algorithm is considered weak and collisions are now practical: The first collision for full SHA-1.Status in SmartFTP: Only offered for compatibility with legacy servers. It will be removed in the near future.

diffie-hellman-group-exchange-sha256, diffie-hellman-group14-sha256

Security Status: DH groups with a group size equal or greater than 2048-bit are secure. Status in SmartFTP: Offered.

Encryption Algorithms

3des-cbc

Known Vulnerability

The attack is impractical for SSH2 because re-keying (when correctly implemented) must happen after every 1 GB of data transferred.

Security Status: Secure when re-keying is properly implemented. However discouraged and aes-ctr and aes-gcm are preferred.Status in SmartFTP: Only offered for compatibility with legacy servers. It will be removed in the near future.