3 ms·
There is actually a reason you can't have ~/.ssh/config symlinked the same way: ssh refuses to read a symlink for this file (for security purposes it is strict
by bdarnell 12y ago
There is actually a reason you can't have ~/.ssh/config symlinked the same way: ssh refuses to read a symlink for this file (for security purposes it is strict about the file type and permissions). My workaround is to copy the file instead of symlinking in my dotfile-setup script.
- voltagex_ 12y agoOops! Thanks for the clarification
- wampus 12y agoI version control the entire directory (ignoring the known_hosts file) somewhere like ~/config/ssh and symlink it to ~/.ssh. It contains a Makefile with a target that runs this command: ln -s ${PWD} ~/.ssh Just make sure the directory is chmod 700 and the important files in it are chmod 600.
- jethro_tell 12y agoAlso ignore any private keys. For security, but also each host should have a different key so you can burn one without burning them all.