You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unpwn checks passwords locally against the top one million passwords, as provided by the nbp project. Then, it uses the haveibeenpwned API to check proposed passwords against the largest corpus of publicly dumped passwords in the world.
As a bonus, if the haveibeenpwned API is down, at least there's still some checks applied.
The text was updated successfully, but these errors were encountered:
Too bad it would render use of https://github.com/philnash/pwned library redundant. I feel like pwned is a more solid library, and certainly seems more configurable, so I'd personally prefer to keep using it (but my bias may be unfounded).
It seems pretty unlikely that the haveibeenpwned API would go down for a significant length of time...
Consider using the unpwn gem to check passwords locally https://github.com/indirect/unpwn
As a bonus, if the haveibeenpwned API is down, at least there's still some checks applied.
The text was updated successfully, but these errors were encountered: