On Tue, Jun 8, 2021 at 9:46 AM Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx> wrote: > > On Tue, Jun 08, 2021 at 03:18:10PM +0200, Björn 'besser82' Esser wrote: ... > > in the future existing yescrypt hashes can be > > updated to new yescrypt hashes with stronger salts and/or cost > > parameters in-place without changing the password, and without user > > interaction. > > Interesting. How does this work? My guess would be that the PAM module that performs the authentication would just re-encrypt and store that password after a successful auth against the previous salt/params. I was thinking about suggesting a similar PAM module to convert existing hashes, but I suspect that we'd be coming up against some issues with security policy and separation of actions. Right now, I expect that SELinux permits PAM processes to have read-only access to /etc/shadow, but such a change would necessitate read/write access, which is riskier. It's also why PAM has separate activities for authentication, authorization and password-change. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
