Bug 1329976
| Summary: | ssh-copy-id fails with shells unaware of ~/ | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Marcel Kolaja <mkolaja> |
| Component: | openssh | Assignee: | Jakub Jelen <jjelen> |
| Status: | CLOSED ERRATA | QA Contact: | Stanislav Zidek <szidek> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.7 | CC: | fkrska, jjelen, ksrot, mkolaja, plautrba, salmy, szidek, tlavigne, zpytela |
| Target Milestone: | rc | Keywords: | EasyFix, Patch, Regression, Reproducer, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1327547 | Environment: | |
| Last Closed: | 2016-05-10 04:19:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1327547 | ||
| Bug Blocks: | |||
|
Description
Marcel Kolaja
2016-04-25 08:31:33 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 |