Cipher suite mystery

[3BK]

Hi Alex.
My client doesn't seem to be able to find some of the slightly more modern algorithms - even though they were explicitly compiled. How can I convince the client to find them ?

I want to be able to specify a strong ciphersuite upon request.
//sess.method_pref(MethodType::Kex, "curve25519-sha256").unwrap();
//sess.method_pref(MethodType::CryptCs,"[email protected]").unwrap();
//sess.method_pref(MethodType::MacCs,"[email protected]").unwrap();

Steps taken

• compiled openssl 3.0.x from scratch using -fPIC
• statically linked openssl
• checked the cipher suite using strace
• observed that modern algos such as gcm appear to be missing

sendto(3, "\0\0\4\254\v\24\t\211 \320JbT\275\375\374\35 ^\30B\235\0\0\1Kcurve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1,diffie-hellman-group-exchange-sha1,ext-info-c\0\0\1\tecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],[email protected],ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa,[email protected],ssh-dss\0\0\0\222aes128-ctr,aes192-ctr,aes256-ctr,aes256-cbc,[email protected],aes192-cbc,aes128-cbc,blowfish-cbc,arcfour128,arcfour,cast128-cbc,3des-cbc\0\0\0\222aes128-ctr,aes192-ctr,aes256-ctr,aes256-cbc,[email protected],aes192-cbc,aes128-cbc,blowfish-cbc,arcfour128,arcfour,cast128-cbc,3des-cbc\0\0\0qhmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160,[email protected]\0\0\0qhmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-sha1-96,hmac-md5,hmac-md5-96,hmac-ripemd160,[email protected]\0\0\0\4none\0\0\0\4none\0\0\0\0\0\0\0\0\0\0\0\0\0:3\254a\363\252\254SK\321\227", 1200, MSG_NOSIGNAL, NULL, 0) = 1200
recvfrom(3, "\0\0\2\334\5\24\313\26_\220VK\230\25;K\277\303\243\362}\26\0\0\0\255curve25519-sha256,[email protected],diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group-exchange-sha256\0\0\0%rsa-sha2-512,rsa-sha2-256,ssh-ed25519\0\0\[email protected],[email protected],aes256-ctr,[email protected],aes192-ctr,aes128-ctr\0\0\[email protected],[email protected],aes256-ctr,[email protected],aes192-ctr,aes128-ctr\0\0\[email protected],[email protected],[email protected],hmac-sha2-512\0\0\[email protected],[email protected],[email protected],hmac-sha2-512\0\0\0\25none,[email protected]\0\0\0\25none,[email protected]\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 16384, MSG_NOSIGNAL, NULL, NULL) = 736

[3BK]

Is it as simple as recompling libssh2?

[yodaldevoid]

This may have been resolved by #334.