ed25519 fingerprint mismatch because of extra padding from AWS `=`
Hello. I'm encountering an interesting scenario where the generated fingerprint for my imported/created ed25519 SSH key is different from the one reported by
And AWS generated the fingerprint:
So, there is extra padding for some reason. Does anyone know why that is so?
As per this page the equal sign at the end is padding to ensure correct Base64 encoding.
Yeah, I know WHAT the equal sign is. :) The question is, why it's there when local workflow doesn't produce it. But I figured it out in the end.
I got it.
From other posts here as well, but the answer is that they are using a base64 sha256 openssl combo like this:
$ cat ~/.ssh/ec2-key.pub | base64 -w0 -d | openssl dgst -binary -sha256 | base64 -w0; echo
Where the pub key was generated from the downloaded ec2 pem key like this:
ssh-keygen -y -f ~/.ssh/ec2-key.pem > ~/.ssh/ec2-key.pub
ed25519 fingerprint mismatch because of extra padding from AWS `=`Gergelyasked 24 days ago
Permission denied (publickey,gssapi-keyex,gssapi-with-mic). when using puttchandradcasked 3 years ago
Windows Server "Password is not available"Accepted AnswerAWS-User-5112352asked 4 months ago
Are ed25519 ssh keys supported in AWS Transfer Family?tim-steinerasked 6 months ago
Anyway to *NOT* get MITM'ed?paul__draperasked 3 years ago
HostKey for SFTP Transfer FamilyAccepted Answerdotmindlabsasked 2 months ago
Add Amplify deploy key to multiple github repositories?speshakasked 3 years ago
Ed25519 SSH public key supportAWS-User-1231313asked 3 months ago
AWS Transfer Authentication FailureAWS-User-0962411asked 4 months ago
SSM fingerprint changedAWS-User-4192343asked 4 months ago