Bug 1329976 - ssh-copy-id fails with shells unaware of ~/
Summary: ssh-copy-id fails with shells unaware of ~/
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openssh
Version: 6.7
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Jakub Jelen
QA Contact: Stanislav Zidek
URL:
Whiteboard:
Depends On: 1327547
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-25 08:31 UTC by Marcel Kolaja
Modified: 2019-10-10 11:58 UTC (History)
9 users (show)

Fixed In Version: openssh-5.3p1-118.el6
Doc Type: Bug Fix
Doc Text:
Previously, the ssh-copy-id utility was unable to copy the SSH key to machines that used a shell that did not recognize the "~/" notation for home directories, such as the SUNWbash shell on SunOS systems. Attempts to use ssh-copy-id failed with the following error message: mkdir: Failed to make directory "~/.ssh"; No such file or directory sh: ~/.ssh/authorized_keys: cannot create The ssh-copy-id code has been modified to avoid using "~/" when referring to a home directory. As a result, copying SSH keys works as expected in the described situation.
Clone Of: 1327547
Environment:
Last Closed: 2016-05-10 04:19:28 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0991 0 normal SHIPPED_LIVE openssh bug fix update 2016-05-10 08:18:20 UTC

Description Marcel Kolaja 2016-04-25 08:31:33 UTC
This bug has been copied from bug #1327547 and has been proposed
to be backported to 6.8 z-stream (EUS).

Comment 9 errata-xmlrpc 2016-05-10 04:19:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0991.html


Note You need to log in before you can comment on or make changes to this bug.