You can leave this blank or add a password for a little extra security (and a lot more typing). Enter passphrase (empty for no passphrase): Note that this will overwrite your old (broken) key. You can just press enter to save it in the default place. The prompt should respond with: Generating public/private rsa key pair.Enter file in which to save the key (/Users/freecodecamp/.ssh/id_rsa): Otherwise, create a new key by running: ssh-keygen -t rsa If the prompt responds with a string that starts with “2048 SHA256” you’re done and don’t need to take any further action. Open up your terminal and type: ssh-keygen -l -f ~/.ssh/id_rsa.pub Step #1: delete your old key and create a new oneįirst, let’s check and make sure you indeed need a new key. Let’s set up your new 2048-bit RSA SSH key. Those extra bits make these new keys substantially harder to crack. But DSA keys can usually only be 1024 bits, while RSA keys can be longer, which is the case with Sierra’s default 2048-bit RSA keys. If you’re wondering why RSA keys are more secure than the old DSA keys, they aren’t inherently so. It turns out Apple decided to quietly force 2048-bit RSA keys on everyone, which has been a mild inconvenience for some, and a confused panic for others. Luckily BerkeleyTrue hadn’t upgraded yet, and was able to add my new SSH keys.
It took me a while to realize what had happened.
When I woke up, I was no longer able to access Free Code Camp’s servers. Then I finally caved one night before going to bed.
I clicked “remind me tomorrow” a few days in a row. Like many developers, I got a notice from Apple bugging me to install its new macOS Sierra. It will walk you through safely updating to Sierra and updating your SSH keys. Do not upgrade to macOS Sierra if you have a cloud server (AWS, Digital Ocean, etc.) Read this post first.
0 kommentar(er)
