Upgrading to MacOS Sierra will break your SSH keys and lock you out

Posted by raisedadead on Friday October 14, 2016 @12:07AM
from the medium.freecodecamp.com dept.

https://medium.freecodecamp.com/upgrading-to-macos-sierra-will-break-your-ssh-keys-and-lock-you-out-of-your-own-servers-f413ac96139a

( 4 comments | 11 points | on HN )

Re:Upgrading to MacOS Sierra will break your SSH keys and lo... by gumby on Friday October 14, 2016 @01:40AM (#12706326)

umm, no. I have 1024 bit keys and they have continued to work fine from my Mac to various servers that have the corresponding public key. (yes they should be updated, but I have larger keys for other servers).

I use the stock ssh in /usr/bin/ssh

Perhaps you had dsa keys? Those were deprecated and support for them was dropped.

[ Parent | on HN ]

Re:Upgrading to MacOS Sierra will break your SSH keys and lo... by jsjohnst on Friday October 14, 2016 @09:43AM (#12707982)

> You can leave this blank or add a password for a little extra security (and a lot more typing).

Please please stop saying things like this. If typing the password is inconvenient to you, store it in your keychain. OS X/macOS makes this trivially easy. Having a pass phrase on your private key is (almost) as important as using a key with sufficient entropy.

[ Parent | on HN ]

Re:Upgrading to MacOS Sierra will break your SSH keys and lo... by rurban on Friday October 14, 2016 @01:31AM (#12706297)

Never heard of ssh-copy-id? Copy & paste public ssh keys is a kindergarden solution.

[ Parent | on HN ]

Re:Upgrading to MacOS Sierra will break your SSH keys and lo... by closeparen on Friday October 14, 2016 @02:32AM (#12706447)

Needing to install something (ssh-copy-id does not ship with OSX) to copy a little bit of text around isn't great either.

[ Parent | on HN ]