[ad_1]
Operating brew set up openssh, renaming the built-in /usr/bin/ssh* executables and operating ssh-keygen -t ed25519 just isn’t sufficient.
Your ssh logins will nonetheless solely use the rsa key as a result of the brand new ed25519 key just isn’t identified (to ssh-agent). ssh-add ~/.ssh/id_ed25519 will return:
Couldn’t add identification xxx: agent refused operation
as a result of Mavericks will run the previous ssh-agent model or under no circumstances. Higher disable launching the built-in ssh-agent utilizing: $ launchctl unload -w /System/Library/LaunchAgents/org.openbsd.ssh-agent.plist. Test with ps -ef that no ssh-agent is operating, in any other case kill that pid.
Now it is time to be taught your terminal shell to begin the newer ssh-agent mechanically, as soon as. When utilizing zsh as shell, run $ nano .zshrc and append this:
# Robotically begin ssh-agent as soon as
if [[ "x" == "x`ps -x -u ${USER} | egrep '[s]sh-agent'`" ]] ; then
ssh-agent | sed -e "/^echo/d" > ${HOME}/.ssh/agent-env
supply ${HOME}/.ssh/agent-env
ssh-add -qk
else
supply ${HOME}/.ssh/agent-env
fi
Now your newly opened terminal periods will use the previous rsa and new ed25519 keys. The keys which are loaded in ssh-agent will be listed with ssh-add -l to confirm.
[ad_2]
