That might happen to users, who didn't change their passwords since 2007 or so, as libxcrypt now reports the use of very unsafe hash methods to PAM.
That is interesting, since this happened with a ~2016 server install, which has been slowly upgraded as time went by. Specifically this was with the 4.4.21 version
Upgrade libxcrypt-4.4.21-1.fc34.x86_64 @updates-testing
Upgraded libxcrypt-4.4.20-2.fc34.x86_64 @@System
Upgrade libxcrypt-compat-4.4.21-1.fc34.x86_64 @updates-testing
Upgraded libxcrypt-compat-4.4.20-2.fc34.x86_64 @@System
Afterwards, at every login prompt it would just prompt me to change my password. The first time it popped back up it was weird, but I went along with it. It logged me out and I attempted to log in again. I hit the same thing, and at this point I decided it was in a loop. Thankfully I had some free time now to utilize a recovery image and chroot into my actual sysroot, and downgrade back to 4.4.20.
Excerpts from journal:
May 27 20:07:02 das-hostname systemd[1]: Starting User Manager for UID USER_ID...
May 27 20:07:02 das-hostname systemd[695]: pam_unix(systemd-user:account): expired password for user das_user (root enforced)
May 27 20:07:02 das-hostname systemd[695]: PAM failed: Authentication token is no longer valid; new one required
May 27 20:07:02 das-hostname systemd[695]: user@USER_ID.service: Failed to set up PAM session: Operation not permitted
May 27 20:07:02 das-hostname systemd[695]: user@USER_ID.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
May 27 20:07:02 das-hostname systemd[1]: user@USER_ID.service: Main process exited, code=exited, status=224/PAM
May 27 20:07:02 das-hostname systemd[1]: user@USER_ID.service: Failed with result 'exit-code'.
May 27 20:07:02 das-hostname systemd[1]: Failed to start User Manager for UID USER_ID.
May 27 20:07:02 das-hostname systemd[1]: Started Session 1 of user das_user.
May 27 20:07:02 das-hostname sshd[692]: pam_unix(sshd:session): session opened for user das_user(uid=USER_ID) by (uid=0)
May 27 20:17:28 das-hostname passwd[697]: pam_unix(passwd:chauthtok): password changed for das_user
May 27 20:17:31 das-hostname systemd[1]: Starting User Manager for UID USER_ID...
May 27 20:17:31 das-hostname systemd[709]: pam_unix(systemd-user:account): expired password for user das_user (root enforced)
May 27 20:17:31 das-hostname systemd[709]: PAM failed: Authentication token is no longer valid; new one required
May 27 20:17:31 das-hostname systemd[709]: user@USER_ID.service: Failed to set up PAM session: Operation not permitted
May 27 20:17:31 das-hostname systemd[709]: user@USER_ID.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
May 27 20:17:31 das-hostname systemd[1]: user@USER_ID.service: Main process exited, code=exited, status=224/PAM
May 27 20:17:31 das-hostname systemd[1]: user@USER_ID.service: Failed with result 'exit-code'.
May 27 20:17:31 das-hostname systemd[1]: Failed to start User Manager for UID USER_ID.
May 27 20:17:31 das-hostname systemd[1]: Started Session 2 of user das_user.
May 27 20:17:31 das-hostname sshd[706]: pam_unix(sshd:session): session opened for user das_user(uid=USER_ID) by (uid=0)
I have not tested 4.4.22 yet, if that improves things. Additionally, are there any hints in f.ex. password -S das_user which would give a hint to the user that they would be hitting issues?
Generally works fine.
Too bad the
drm/vmwgfxfixes for their previous changes merged as part of 6.10.4 don't seem to be fixing non-working graphics for me :/ Thus leaving me still on 6.10.3 for my local virtual machine usage.I guess it's time to attempt to build my own kernel with some additional DRM/vmware surface format logging to see what the mode and DRM surface types are...