Timeline for ssh prompts for password despite ssh-copy-id
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 15, 2020 at 0:01 | comment | added | Dan H | The logic to the above (which helps explain WHY you do it, which then helps me remember to do it) is this: the g+w permission on a directory lets you create, move, or rename its contents. Thus if your .ssh dir is set to g-w, but $HOME is set to g+w... then someone in that group could rename your .ssh dir to .junk (because g+w on $HOME allows that), and create a new (and "fraudulent") .ssh directory. | |
| Sep 28, 2011 at 14:19 | comment | added | Ben Kreeger | This was it, for me. I used ssh-copy-id to send over an RSA key, and I was still getting prompted. Running chmod g-w homedir on the remote server worked like a charm. | |
| Dec 2, 2010 at 19:59 | comment | added | Gilles 'SO- stop being evil' | Yup. ssh-copy-id should have taken care of the permissions of ~/.ssh and ~/.ssh/authorized_keys, but also make sure that your home directory itself isn't group-writable. | |
| Dec 2, 2010 at 14:48 | history | answered | user732 | CC BY-SA 2.5 |