Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionRichard W.M. Jones
2015-09-07 21:21:32 UTC
NOTE: Do NOT affect RHEL 7.2. Cloning the bug just so we
check that the patch is included in RHEL 7.3 (assuming we
do the rebase).
+++ This bug was initially created as a clone of Bug #1260778 +++
Description of problem:
When using virt-builder --ssh-inject, the permissions of ~/.ssh and ~/.ssh/authorized_keys are not set appropriately.
Version-Release number of selected component (if applicable):
Checked in latest available Fedora non-testing version
(libguestfs-tools-c-1.30.0-1.fc22.x86_64)
How reproducible:
Hmmm. 100% it seems.
Steps to Reproduce:
1. virt-builder <TEMPLATE> --ssh-inject root
2. Import image with virt-install or use guestfish/guestmount to pull up rootfs
3. Execute: ls -la /root/.ssh
Actual results:
total 4
drwxr-xr-x. 2 root root 28 Sep 7 13:04 .
dr-xr-x---. 3 root root 97 Sep 7 13:04 ..
-rw-r--r--. 1 root root 397 Sep 7 13:04 authorized_keys
Expected results:
total 4
drwx------. 2 root root 28 Sep 7 13:04 .
dr-xr-x---. 3 root root 97 Sep 7 13:04 ..
-rw-------. 1 root root 397 Sep 7 13:04 authorized_keys
--- Additional comment from Ryan Sawhill on 2015-09-07 14:05:47 EDT ---
When the ssh-copy-id command creates ~/.ssh and ~/.ssh/authorized_keys it sets the perms to 0700 and 0600, respectively.
That said, in my email correspondence, I was wrong to suggest that --ssh-inject was failing for me because of this. Turns out it was a quirk of my current setup with ssh-agent and too many keys.
I still think it would be a good idea to set the same perms that ssh-copy-id does, but not that big of a deal I guess.
--- Additional comment from Richard W.M. Jones on 2015-09-07 16:43:13 EDT ---
I looked at ssh-copy-id and ssh and both are creating ~/.ssh with
mode 0700, so that looks like the right thing to do.
--- Additional comment from Richard W.M. Jones on 2015-09-07 17:17:21 EDT ---
Patch posted:
https://www.redhat.com/archives/libguestfs/2015-September/msg00021.html
Verified with the packages:
libguestfs-1.32.5-6.el7.x86_64
Verify steps:
1. Build a Fedora guest image and inject your public key and a string to the guest:
# virt-builder fedora-23 --arch i686 -o fedora-23.img --ssh-inject root:file:/root/.ssh/id_rsa.pub --ssh-inject root:string:"ssh-rsa AAtesttesttest"
Command finished successfully and there should be a image: fedora-23.img2.
2. Check the permission:
# guestfish -a tmp.qcow2 -i ll /root/.ssh/
drwx------ 2 root root 28 Jun 21 09:14 .
dr-xr-x---. 5 root root 4096 Jun 21 09:14 ..
-rw------- 1 root root 402 Jun 21 09:14 authorized_keys
The permission of .ssh is 0700 and authorized_keys is 0600.
So verified.
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/RHSA-2016-2576.html