I tried to use my ed25519 public key to create a new VM. It doesn't work, since Azure in general doesn't support these keys. See: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/ed25519-ssh-keys
But I honestly don't get why this isn't supported.
Another issue here: The input field error for SSH Public Key is also misleading. It says: "Multiline SSH key must begin with '---- BEGIN SSH2 PUBLIC KEY ----' and end with '---- END SSH2 PUBLIC KEY ----'."
Describe the solution you'd like
I'd like to be able to use ed25519 public keys and/or a non-misleading error message, when another/wrong key is being used.
Describe alternatives you've considered
I need to create a separate rsa key for my client machine. This is kinda tedious since we agreed to use ed25519 in our company.
BUT.. I'm also not sure if we could circumvent this issue by modifying the authorized_keys file ourselve.
Additional context
There have been issues here which addressed this exact issue but went stale and ultimately have been closed:
Azure/AKS#2850
Azure/AKS#1172
Azure/AKS#3434
I tried to use my ed25519 public key to create a new VM. It doesn't work, since Azure in general doesn't support these keys. See: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/ed25519-ssh-keys
But I honestly don't get why this isn't supported.
Another issue here: The input field error for SSH Public Key is also misleading. It says: "Multiline SSH key must begin with '---- BEGIN SSH2 PUBLIC KEY ----' and end with '---- END SSH2 PUBLIC KEY ----'."
Describe the solution you'd like
I'd like to be able to use ed25519 public keys and/or a non-misleading error message, when another/wrong key is being used.
Describe alternatives you've considered
I need to create a separate rsa key for my client machine. This is kinda tedious since we agreed to use ed25519 in our company.
BUT.. I'm also not sure if we could circumvent this issue by modifying the authorized_keys file ourselve.
Additional context
There have been issues here which addressed this exact issue but went stale and ultimately have been closed:
Azure/AKS#2850
Azure/AKS#1172
Azure/AKS#3434