Check your password security with Have I Been Pwned? and pass

Periodically checking for password compromise is an excellent way to help ward off most attackers in most threat models.
167 readers like this
167 readers like this

freeGraphicToday, via Pixabay. CC0.

Password security involves a broad set of practices, and not all of them are appropriate or possible for everyone. Therefore, the best strategy is to develop a threat model by thinking through your most significant risks—who and what you are protecting against—then model your security approach on the activities that are most effective against those specific threats. The Electronic Frontier Foundation (EFF) has a great series on threat modeling that I encourage everyone to read.

In my threat model, I am very concerned about the security of my passwords against (among other things) dictionary attacks, in which an attacker uses a list of likely or known passwords to try to break into a system. One way to stop dictionary attacks is to have your service provider rate-limit or deny login attempts after a certain number of failures. Another way is not to use passwords in the "known passwords" dataset.

Check password security with HIBP

Troy Hunt created Have I Been Pwned? (HIBP) to notify people when their information is found in leaked data dumps and breaches. If you haven't already registered, you should, as the mere act of registering exposes nothing. Troy has built a collection of over 550 million real-world passwords from this data. These are passwords that real people used and were exposed by data that was stolen or accidentally made public.

The site does not publish the plaintext password list, but it doesn't have to. By definition, this data is already out there. If you've ever reused a password or used a "common" password, then you are at risk because someone is building a dictionary of these passwords to try right now.

Recently, Firefox and HIBP announced they are teaming up to make breach searches easier. And the National Institutes of Standards and Technology (NIST) recommends that you check passwords against those known to be compromised and change them if they are found. HIBP supports this via a password-checking feature that is exposed via an API, so it is easy to use.

Now, it would be a bad idea to send the website a full list of your passwords. While I trust, it could be compromised one day. Instead, the site uses a process called k-Anonymity that allows you to check your passwords without exposing them. This is a three-step process. First, let's review the steps, and then we can use the pass-pwned plugin to do it for us:

  1. Create a hash value of your password. A hash value is just a way of turning arbitrary data—your password—into a fixed data representation—the hash value. A cryptographic hash function is collision-resistant, meaning it creates a unique hash value for every input. The algorithm used for the hash is a one-way transformation, which makes it hard to know the input value if you only have the hash value. For example, using the SHA-1 algorithm that HIBP uses, the password hunter2 becomes F3BBBD66A63D4BF1747940578EC3D0103530E21D.
  2. Send the first five characters (F3BBB in our example) to the site, and the site will send back a list of all the hash values that start with those five characters. This way, the site can't know which hash values you are interested in. The k-Anonymity process ensures there is so much statistical noise that it is hard for a compromised site to determine which password you inquired about. For example, our query returns a list of 527 potential matches from HIBP.
  3. Search through the list of results to see if your hash is there. If it is, your password has been compromised. If it isn't, the password isn't in a publicly known data breach. HIBP returns a bonus in its data: a count of how many times the password has been seen in data breaches. Astoundingly, hunter2 has been seen 17,043 times!

Check password security with pass

I use pass, a GNU Privacy Guard-based password manager. It has many extensions, which are available on the pass website and as a separately maintained awesome-style list. One of these extensions is pass-pwned, which will check your passwords with HIBP. Both pass and pass-pwned are packaged for Fedora 29, 30, and Rawhide. You can install the extension with:

sudo dnf install pass pass-pwned

or you can follow the manual instructions on their respective websites.

If you're just getting started with pass, read Managing passwords the open source way for a great overview.

The following will quickly set up pass and check a stored password. This example assumes you already have a GPG key.

# Setup a pass password store
$ pass init <GPG key email>

# Add the password, "hunter2" to the store
$ pass insert

# Install the pass-pwned extension
# Download the bash script from the upstream and then review it
$ mkdir ~/.password-store/.extensions
$ wget -O ~/.password-store/.extensions/pwned.bash
$ vim ~/.password-store/.extensions/pwned.bash

# If everything is OK, set it executable and enable pass extensions
$ chmod u+x ~/.password-store/.extensions/pwned.bash
$ echo 'export PASSWORD_STORE_ENABLE_EXTENSIONS="true"' >> ~/.bash_profile
$ source ~/.bash_profile

# Check the password
$ pass pwned
Password found in haveibeenpwned 17043 times

# Change this password to something randomly generated and verify it
$ pass generate -i
The generated password for is:
$ pass pwned
Password not found in haveibeenpwned

Congratulations, your password is now more secure than it was before! You can also use wildcards to check multiple passwords at once.

Periodically checking for password compromise is an excellent way to help ward off most attackers in most threat models. If your password management system doesn't make it this easy, you may want to upgrade to something like pass.

What to read next
Brian "bex" Exelbierd is the RHEL Community Business Owner and works to inform the RHEL roadmap with community efforts and to support Operating System communities. At Red Hat, Brian has worked as a technical writer, software engineer, content strategist, community architect and now as a product manager.


Consider a folliw-up... People crib passwords because good ones are hard [read, impossible] to remember and those easy to remember [read, short] are often terrible. So called "pronouncible" a can be long enough and memorable.

Choosing good passwords was out of scope for this article, however, I tend to agree with your thoughts. There are both memorable/prouncounceable systems, similar to the one proposed in XKCD and completely generated passwords such as those done by pass which tend to be random. I personally follow a policy of having completely random passwords (as long as allowed by the site) generated by my password manager. I never type them directly because the password manager remembers them for me.

In reply to by Daniel M St-Andre (not verified)

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.