 |
Thank you for the report. What you're seeing appears to be expected behavior. The -p option takes the value as-is and places it into /etc/shadow. The man page section on this option implies as such. -p, --password PASSWORD The encrypted password, as returned by crypt(3). Note: This option is not recommended because the password (or encrypted password) will be visible by users listing the processes. You should make sure the password respects the system's password policy. Newer distributions (such as Fedora) provide a better description on the value expected. Below is says "defines", which implies that whatever you provide is exactly what will be put in /etc/shadow. -p, --password PASSWORD defines a new password for the user. PASSWORD is expected to be encrypted, as returned by crypt (3). Note below where I provide an already hashed/salted string and it places it in. [root@awx ~]# grep testuser1 /etc/shadow testuser1:newpw456:20059:7:84:7:30:: [root@awx ~]# usermod -p '$6$hP/3KrsjMHb01VXg$D5K3FvFaNqFYUUZM7H0RIaryD23Gfdlv7RkILvUk3Rd40NWv6efQ0JeWnczp24TEiF/b3MG26ymkgHs8aoR23/' testuser1 [root@awx ~]# grep testuser1 /etc/shadow testuser1:$6$hP/3KrsjMHb01VXg$D5K3FvFaNqFYUUZM7H0RIaryD23Gfdlv7RkILvUk3Rd40NWv6efQ0JeWnczp24TEiF/b3MG26ymkgHs8aoR23/:20059:7:84:7:30:: You should continue to use the standard passwd command to change local user passwords if you want the login.defs settings to be honored. Closing as not a bug. shadow-utils source: https://github.com/shadow-maint/shadow |
- Anonymous
