No matter what I do, I cannot seem to get ssh-keygen to create an RSA key accepted by Google Compute Console's ssh key .. page.

Slackware's ssh creates an RSA that works immediately without issue. However, even though the compute VM (also 15.3 with the same ssh version as local) accepts the key created in Slackware, the one created on the local OpenSuse 15.3 is not seen as valid.

Copying the key to Slackware and running ssh-keygen -l -f on the file also returns that it is not a valid public key. I've tried changing bit sizes (2048, 3072 etc) as well as adding (and not adding) the -m pem flag.

I also created an RSA on the compute OpenSuse machine and copied it to the local, and despite them all running the same version, the local machine claimed the key was invalid. So basically.. the local machine generates keys that aren't valid, and everything that is valid to (everything else) is seen as being invalid to the same local 15.3 install.

What am I missing..?


Note: solved. The keygen was adding new line characters at the end of random blocks. Doing a cat -e on the file will show you the weirdness. Remove them and try again if you experience this..

It's better if you post solutions as a follow-up post, because:

1) it removes the thread from the list of "Zero Reply Threads".
2) it causes anyone who might have subscribed to get notified (which editing doesn't do).