Public bug reported:
The ssh-copy-id man-page contains a passage which states:
"It also changes the permissions of the remote user’s home, ~/.ssh, and
~/.ssh/authorized_keys to remove group writability (which would
otherwise prevent you from logging in, if the remote sshd has
StrictModes set in its configuration)."
However, aside from setting an appropriate umask before creating a .ssh
directory (if none exists), it doesn't do this. In particular, if .ssh
exists and is group-writable, then it will remain group-writable,
causing the key to be ignored by sshd if StrictModes is on.
A sane fix would seem to be either removing the man-page's paragraph
(perhaps replacing it with one warning about setting proper directory
permissions) or implementing the functionality it indicates (i.e. chmod
g-w .ssh at some point).
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
ssh-copy-id doesn't actually change permissions
https://bugs.launchpad.net/bugs/156049
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
