Dmitri

bjarke, It is CentOS 7.6 running the latest opensshd. It's possible that the configuration is altered to disable the other cyphers, or it's just binary compiled without WITH_OPENSSL option. As of Cryptlib - I contacted author and sent him patch that makes AES-CTR available for SSH connections. With versions up to 3.4.4.1 it's not available. Author replied that he is aware of that problem and already got his own fix. It's unclearthough whether and when he's going to publish it.

openssh sources: https://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/cipher.c?rev=1.112&content-type=text/x-cvsweb-markup see how ciphers are defined: static const struct sshcipher ciphers[] = { #ifdef WITH_OPENSSL { "3des-cbc", 8, 24, 0, 0, CFLAG_CBC, EVP_des_ede3_cbc }, { "aes128-cbc", 16, 16, 0, 0, CFLAG_CBC, EVP_aes_128_cbc }, { "aes192-cbc", 16, 24, 0, 0, CFLAG_CBC, EVP_aes_192_cbc }, { "aes256-cbc", 16, 32, 0, 0, CFLAG_CBC, EVP_aes_256_cbc }, { "rijndael-cbc@lysator.liu.se", 16, 32, 0,...

Situation is even worse -- even the latest cryptlib 3441 does not support aes*-ctr ciphers, so the IDE with built-in ssh/sftp won't work with any recent linux distro that is shipped with openssh built wihtout openssl because such sshd won't offer any ciphers other than aes*-ctr and some thing called chacha. I discovered this problem by debugging the IDE -- the following lines is where this error is obtained from criptolib: CHAR szError[200] = { 0 }; int ccbSize = sizeof(szError) - 1; clib.cryptGetAttributeString(cryptSession,...