Please, consider adapting the Dashboard to allow the adding of Ed25519 keys for SSH sessions.

RSA, the cryptographic method currently in place for SSH sessions, is mathematically breakable, which is why long keys are necessary to keep security; nevertheless, there is always the possibility they could be cracked. Also, for long term protection, RSA keys should now, supposedly, contain at least 15360 bits; of course, this is unrealistic in a real environment, as it decreases performance and increases strain on the communication channels.

I pledge for the usage of Ed25519, considering a mere 256 bit key is enough to guarantee long term protection, simplifying drastically the identities used for logging into servers and increasing security all at the same time.

OpenSSH, the SSH software ran on most Linux servers, just like my Cloudways Digital Ocean droplet, has supported Ed25519 cryptography since v6.5, released in January 2014, meaning most servers should support it out of the box. My specific server runs OpenSSH v7.4, for example, many releases ahead of the one with the Ed25519 implementation.

Even though it might sound a little tricky, this suggestion should not be too complicated to implement: the software to handle these cryptographic method is already in place in most, if not all servers, so the only thing necessary to get this online is a change in the front-facing console, or Dashboard, clients like me use to configure their servers. It would, however, significantly improve security for SSH connections and make them airtight for the future, as well as tranquilising the few of us, such as myself, who dread of seeing their RSA keys cracked by someone malicious.

Once again, please consider taking action on this.