Skip to content

Handle ConvPutAuthAbort as an authentication failure

Gibeom Gwon requested to merge gbgwon/kscreenlocker:systemd-homed-fix into master

If an incorrect password is provided for a systemd-homed based user, kcheckpass sends ConvPutAuthAbort. Currently, ConvPutAuthAbort is handled like ConvPutReadyForAuthentication. This causes the problem of repeating authentication indefinitely. So, treating ConvPutAuthAbort as an authentication failure solves the problem.

To reproduce the problem:

  1. Create systemd-homed based user.
  2. Make sure PAM configure supports systemd-homed.
  3. Try unlock in lockscreen.(not SDDM login screen)

You can easily reproduce this with arch linux. If you enter an incorrect password, notification says login is blocked by too many login attempts.

Merge request reports