Skip to content

Feature request :: change pass :: check against haveibeenpwned.com #129

Open

Description

@adriansev

Hi! Would be possible that for changing password to check it against haveibeenpwned.com ?
Unfortunately i have no perl knowledge and i cannot contribute directly but if it helps
this is the python version of checking: https://github.com/adriansev/bin-scripts/blob/master/check_pass_pwned

Thanks a lot!

Activity

  1. jcameron commented on Sep 30, 2025

    @jcameron
    Collaborator

    Interesting idea ... although I feel like actually it would be more useful to do this check against existing accounts, rather than when the password is changed.

  2. adriansev commented on Oct 1, 2025

    @adriansev
    Author

    well, it's not possible as the input for checking is the sha1 while what is stored in passwd is sha512. the leaked password are in clear text, so the usage of sha1 is the minimum thing to make the checking faster (i suppose) also allowing to make the checking local (by downloading all hashes with the given prefix)

  3. jcameron commented on Oct 1, 2025

    @jcameron
    Collaborator

    Hmm ... in that case, checking at password change time is less valuable since it doesn't happen very often.

  4. adriansev commented on Oct 2, 2025

    @adriansev
    Author

    Hmm ... in that case, checking at password change time is less valuable since it doesn't happen very often.

    I would say is valuable enough to check if the password is already in leak passwords databases or in rainbow tables.. and the password change can happen when you increase the security of the password or one want to make sure that the password is somewhat safe ..
    Nextcloud software have this nice trick implemented for it's users, i thought that it may be useful also for usermin, as i did not find a way to implement this at pam level.

  5. github-actions commented on May 21, 2026

    @github-actions

    Closing this issue automatically because there has been no follow-up for 3 months.

  6. iliaross commented on May 21, 2026

    @iliaross
    Collaborator

    Reopened, as this was closed by an automated cleanup run.

    ⚠️ If the issue is resolved, please take a moment to close it to help keep the project organized.

  7. added
    Needs TriageReminded once after a long quiet period; needs a maintainer decision
    on Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Needs TriageReminded once after a long quiet period; needs a maintainer decision

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions