For some reason in 4.1.1.0 I get back an error dialog from a messaging seemingly from libssh complaining about not being able to use the aes256-gcm cipher (I can ssh with vanilla ssh to the server just fine). This cipher is not blacklisted and I can connect to clients with this cipher just fine. Here's some output from ssh with -vv, where it shows the key exchange works just fine: debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: aes256-gcm@openssh.com MAC: <implicit> compression: none debug1: kex: client->server cipher: aes256-gcm@openssh.com MAC: <implicit> compression: none (I get prompted for a password and can log in). It's definitely something fishy with x2goclient.
Perhaps this was user error, I'm not sure, but I can't reproduce this issue, anymore.
