Comprehensive data protection for all workloads
- Posts: 1
- Liked: 5 times
- Joined: Feb 07, 2019 5:48 pm
- Full Name: Jeff M
When enabling guest processing for linux VMs, currently keys must be in ssh.com format and not SSH2. Tutorials exist for using PuTTYgen to convert to the ssh.com format. However, ed25519 keys cannot be converted, since the ssh.com format was deprecated before the development of ed25519.
In short, we have deployed ed25519 keys extensively in our environment, and eliminated RSA keys. While recent versions of PuTTY have no problem using ed25519 keys, and it's been the default for OpenSSH on linux since 2014, Veeam can't import them because they can only be created in SSH2 format, and not the older ssh.com format.
- VP, Product Management
- Posts: 5544
- Liked: 2361 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
Even if you could import these keys, they won't work, because the current SSH libraries in use doesn't have support for any elliptical curve algorithms. So this request is really to add support for the ed25519 algorithm to the product, so that it can support such keys. It's a good request, one that I've recently voiced myself internally, but unfortunately, is non-trivial. That's not to say it's not important, or shouldn't be done, but only to set proper expectations that it might not be right around the corner.
Users browsing this forum: Google [Bot] and 30 guests