Minor change to SSH settings
We’re making a minor technical change to the SSH settings our servers use, removing obsolete and insecure ciphers like “3des-cbc”.
The changes are required to ensure that sites we host pass PCI compliance scans. The obsolete ciphers allowed SSH connections that appeared to be secure, but really weren’t.
This should not affect anything for our customers who use SSH, as long as you use modern, updated SSH software. We’re just documenting it in case anyone has difficulties with SSH connections.
If you do have any trouble, the solution is almost certainly to update your SSH client software, though — the program you’re using is probably pretty outdated and may also have trouble connecting to other servers, not just ours.
As always, don’t hesitate to contact us if you have any trouble or questions.
Can you provide more technical details?
If you’re an expert in SSH and wondering precisely what has been disabled and what is available, here’s a list:
These are ciphers, etc., that we no longer support:
Disabled KexAlgorithms: diffie-hellman-group-exchange-sha1, diffie-hellman-group14-sha1, diffie-hellman-group1-sha1
Disabled Ciphers: 3des-cbc, blowfish-cbc, cast128-cbc, arcfour, arcfour128, arcfour256
Disabled MACs: hmac-md5, hmac-md5-96, hmac-sha1, hmac-sha1-96, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com
These are ciphers, etc., that you can use. Your SSH software should work as long as it supports at least one in each group:
KexAlgorithms: firstname.lastname@example.org, ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group-exchange-sha256
Ciphers: aes128-ctr, aes192-ctr, aes256-ctr, email@example.com, firstname.lastname@example.org, email@example.com, aes128-cbc, aes192-cbc, aes256-cbc
MACs: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, hmac-sha2-256, hmac-sha2-512, hmac-ripemd160