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.
Bug 1143949 - virt-customize option '--password-crypto' do not work
Summary: virt-customize option '--password-crypto' do not work
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Richard W.M. Jones
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1143942 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-18 10:07 UTC by Lingfei Kong
Modified: 2015-03-05 13:45 UTC (History)
5 users (show)

Fixed In Version: libguestfs-1.27.49-1.1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 13:45:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0303 0 normal SHIPPED_LIVE libguestfs bug fix and enhancement update 2015-03-05 17:34:44 UTC

Description Lingfei Kong 2014-09-18 10:07:31 UTC 
Description of problem:
virt-customize option '--password-crypto' md5|sha256|sha512 do not work, if you set password encryption to a new value md5, then create a new user and set its password, the new password will stil use the old password encryption, such as sha512.


Version-Release number of selected component (if applicable):
libguestfs-1.27.48-1.1.el7


How reproducible:
100%


Steps to Reproduce:
1. Create a raw format guest image: rhel6.6.img, by default this guest use 'sha512' as its password encryption
2. #virt-customize --password-crypto sha256 -a rhel6.6.img
[   0.0] Examining the guest ...
[   6.0] Setting a random seed
[   6.0] Finishing off


3. Login the guest, create a new user and check file /etc/shadow and /etc/sysconfig/authconfig
# useradd test
# passwd test
#cat /etc/shadow/ | grep test
test:$6$yg/Rmp2s$nldShmCkNxZNyaubkqMEyLAWnhwEXczkzVK5SaQb3qktvxHIXQ5kgoFjVNkQRZHyIW.Mb742x7SkxL8NdWgrW/:16331:0:99999:7:::
#cat /etc/sysconfig/authconfig | grep PASSWDALGORITHM
PASSWDALGORITHM=sha512


Actual results:
The hashing algorithm in /etc/shadow is still sha512, i.e. the first two characters in the password field is $1 (md5 - 1, sha512 - 6, sha256 - 5)
The value of PASSWDALGORITHM is still sha512 in /etc/sysconfig/authconfig


Expected results:
The hashing algorithm in /etc/shadow should be md5, i.e. the first two characters in the password field should be $1
The value of PASSWDALGORITHM should be md5 in /etc/sysconfig/authconfig


Additional info:
Comment 1 Richard W.M. Jones 2014-09-18 12:49:13 UTC 
*** Bug 1143942 has been marked as a duplicate of this bug. ***
Comment 2 Richard W.M. Jones 2014-09-18 12:57:35 UTC 
This is a misunderstanding of what the --password-crypto option actually
does.  It only changes the password crypto used by virt-customize, it
doesn't change the crypto of the guest itself.

I have updated the documentation to make this clearer:

https://github.com/libguestfs/libguestfs/commit/e5dd3b08de331b14aee4f86eef373e3c900d8b61

       --password-crypto md5|sha256|sha512
           When the virt tools change or set a password in the guest, this
           option sets the password encryption of that password to "md5",
           "sha256" or "sha512".
[...]
           Note this does not change the default password encryption used by
           the guest when you create new user accounts inside the guest.  If
           you want to do that, then you should use the --edit option to
           modify "/etc/sysconfig/authconfig" (Fedora, RHEL) or
           "/etc/pam.d/common-password" (Debian, Ubuntu).
Comment 4 Lingfei Kong 2014-11-11 08:44:01 UTC 
Verify with libguestfs-1.28.1-1.9.el7

Steps to verify:
1. Prepare a rhel guest image: rhel.img

2. Create a user account 'test' on that guest and check its password encryption: $6(sha512)

3. # virt-customize -a rhel.img --password test:password:testpassword20 --password-crypto md5

4. # qemu-kvm  -m 1024M -smp 3 -drive file=$PWD/rhel.img -vnc :1

5. Access the guest via vncviewer and login account 'test' with password 'testpassword20' and check its password encryption

Results:
Can login account 'test' with the new password 'testpassword20',  and the password encryption in /etc/shadow is $1(md5)
Comment 6 errata-xmlrpc 2015-03-05 13:45:18 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-2015-0303.html
Note You need to log in before you can comment on or make changes to this bug.