Tag Info

New answers tagged


Here you go: find /path/to/keys/directory -type f -name "*.pub" -exec ssh-keygen -lf {} \; | awk '{print $2}' Edit: Whops, ok. get it now. here you go: while read line; do ssh-keygen -lf "$line"; done < <(cat authorised_keys_file) (if this file have one key per line)


From serverfault: You can easily make it a function in your .bashrc: function fingerprints() { local file="$1" while read l; do [[ -n $l && ${l###} = $l ]] && ssh-keygen -l -f /dev/stdin <<<$l done < $file } and then do: $ fingerprints .ssh/authorized_keys


Configuring an SSH server to accept any password would be easy with PAM — put pam_permit on the auth stack, and voilà. The possibility of misconfiguring such an open system is inherent to the flexibility of PAM — since it lets you chain as many tests as you want, the possibility of doing 0 tests is unavoidable (at least without introducing weird exceptions ...


An addition for @Jenny D's answer, from man ssh: ~/.ssh/ This directory is the default location for all user-specific con‐ figuration and authentication information. There is no general requirement to keep the entire contents of this directory secret, but the recommended permissions are read/write/execute ...


Here's the culprit: drwxrwxr-x 2 emerg wheel 4096 Apr 10 11:51 .ssh/ You're allowing anyone in the group wheel write access to your .ssh directory. This means that any member of that group could replace your authorized_keys file - so SSH refuses to trust the file. Fix your permissions and the problem should go away.


A key pair is not tied to you as a user or your machine. Imagine having the keys to your house stolen. The keys aren't bound to you, anyone can use them to unlock your doors. In the exact same way, if I get my hands on your private key, I can use it to make changes to your Github repositories. If you wish to access your repositories using both your new keys ...

Top 50 recent answers are included