SG2218 using SHA-1 for SSH key signatures
I just discovered that my brand new TP-Link SG2218, running firmware released earlier this year, will only use SHA-1 signatures for SSH key-based authentication. SHA-1 was deprecated in 2011, because it is known to be insecure. Sometime in the last few years, Fedora completely disabled SHA-1 in its default system-wide crypto policy. It is literally impossible to SSH to one of these things (if one has any SSH keys set up) without reducing the system-wide crypto level.
I don't expect network equipment vendors to move fast, nor do I expect them to keep updating EOL equipment, but that is not what is happening here. This is a brand new managed switch, running its most recent firmware that was released in 2025. There is absolutely no excuse for this level of pure laziness.
Hi @ipilcher , I checked, and it seem already support SHA2, and it supports RSA-SHA2-256 by default, which uses SHA2 as the key signature algorithm. Could you please share us where do you get the information about SHA1 at TL-SG2218 V1 / FW 1.20.9 ? And could you please help to upgrade to the lasted FW and check?
