Timeline for SSH asking for password after ssh-copy-id
Current License: CC BY-SA 3.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 31, 2012 at 20:21 | comment | added | utopiabound | @WarrenYoung ssh-copy-id only takes care of setting permissions if it creates the files. If they already exist it doesn't alter/correct permissions. | |
| May 31, 2012 at 12:19 | comment | added | lcguida | @Tim I've created the key with ssh-keygen Just typed that, no paraphrase, didn't change the default names of the files Then I copied the key using ssh-copy-id user@remote-host Also tried with the -i argument pointing the file id_rsa.pub in .ssh folder | |
| May 30, 2012 at 23:20 | comment | added | Gilles 'SO- stop being evil' | The readable bit at the end of the line is a comment, it doesn't matter. | |
| May 30, 2012 at 20:57 | comment | added | Warren Young | @Rockskull: Can you also post what you get in /var/log/secure and/or auth.log when you make this login attempt? | |
| May 30, 2012 at 20:24 | comment | added | Tim | @Rockskull the extra verbose output seems to be giving a clue: debug3: no such identity: /home/leandro/.ssh/id_dsa. What is the actual command you are using? | |
| May 30, 2012 at 20:24 | comment | added | Tim | @Rockskull the 'me@host' at the end of the file is normal, the hostname varies depending on the distro or openssh build. | |
| May 30, 2012 at 19:12 | comment | added | lcguida | @Tim I've updated the output with the additional verbose | |
| May 30, 2012 at 19:12 | history | edited | lcguida | CC BY-SA 3.0 | added 5665 characters in body |
| May 30, 2012 at 19:04 | comment | added | Tim | Does appending additional "verbose" switches provide you with more relevant data? example: ssh -vvv | |
| May 30, 2012 at 18:56 | history | edited | lcguida | CC BY-SA 3.0 | added 273 characters in body |
| May 30, 2012 at 18:52 | comment | added | lcguida | Yes, I put the correct user in the format ssh-copy-id user@remote-host Also tried ssh-copy-id -i /home/me/.ssh/<priv_key_name> | |
| May 30, 2012 at 15:48 | answer | added | Huygens | timeline score: 2 | |
| May 30, 2012 at 15:16 | answer | added | Tim | timeline score: 1 | |
| May 30, 2012 at 15:07 | comment | added | Kevin | Rockskull, did you remember to provide the correct username? | |
| May 30, 2012 at 15:06 | comment | added | Kevin | @WarrenYoung the client side perms are correct, yes, but the server side isn't seeing any of the keys as valid, so there's something going on. | |
| May 30, 2012 at 15:06 | comment | added | Warren Young | @Rockskull: The user names are apparently different on both hosts. Did you say ssh-copy-id myuser@remotehost, or just ssh-copy-id remotehost? Check that a copy of ~/.ssh/id-rsa.pub on localhost exists in ~/.ssh/authorized_keys on remotehost. | |
| May 30, 2012 at 15:04 | comment | added | Warren Young | @utopiabound: I don't believe this to be a permissions issue. For one, ssh-copy-id takes care of that, and it's one of the best reasons to use it instead of the older manual method. For another, you see ssh trying to use the keys instead of skipping them, which means at least the client side perms are correct. | |
| May 30, 2012 at 14:56 | answer | added | George M | timeline score: 3 | |
| May 30, 2012 at 14:50 | comment | added | utopiabound | Can you double check the permissions on the foreign host? SSHd can be pretty picky. | |
| May 30, 2012 at 14:43 | history | asked | lcguida | CC BY-SA 3.0 |