# kdbxpasswordpwned
Check keepass passwords against https://haveibeenpwned.com/Passwords
[](https://travis-ci.org/fopina/kdbxpasswordpwned)
[](https://coveralls.io/github/fopina/kdbxpasswordpwned?branch=master)
[](https://microbadger.com/images/fopina/kdbxpasswordpwned)
[](https://microbadger.com/images/fopina/kdbxpasswordpwned)
[](https://pypi.python.org/pypi/kdbxpasswordpwned)
[](https://pypi.python.org/pypi/kdbxpasswordpwned)
### Disclosure
Even if Troy Hunt's API does provide some sense of privacy (as we don't share the password nor even the full SHA1), always review the tools you use with your KeePass files (such as this script which is small and you can easily see the password is not sent anywhere except HIBP API). I have reviewed libkeepass code (0.3.0, pinned in requirements) which is also small, and, as PyPI does not allow replacing existing versions, it is safe.
Also be sure to install tools you trust from places you trust or you might end up installing some shady version such as [this fork](https://github.com/fopina/kdbxpasswordpwned/compare/master...SlivTaMere:bea0f5c) which sends the full password (not the hash) to a different endpoint.
### Usage
Install using `pip`
```bash
$ pip install kdbxpasswordpwned
Collecting kdbxpasswordpwned
Successfully installed kdbxpasswordpwned-0.3
```
And use the CLI
```bash
$ kdbxpasswordpwned -h
usage: kdbxpasswordpwned [-h] [-k KEYFILE] [-u] [-p] kdbx
positional arguments:
kdbx keepass file
optional arguments:
-h, --help show this help message and exit
-k KEYFILE, --keyfile KEYFILE
Keyfile if needed
-u, --show-user show username for found entries
-p, --show-password show password for found entries (high shoulders?)
```
```bash
$ kdbxpasswordpwned /path/to/test_assets/sample.kdbx
Password:
Password for title1 seen 1151 times before
Password for title2 seen 61164 times before
```
Or simply use the docker image
```bash
$ docker run --rm -ti \
-v /path/to/test_assets/sample_with_key.kdbx:/tmp.kdbx:ro \
-v /path/to/test_assets/sample.key:/tmp.key:ro \
fopina/kdbxpasswordpwned -upk /tmp.key /tmp.kdbx
Password for title1 seen 1151 times before - testuser - testit
Password for title2 seen 61164 times before - None - blabla
```
Check keepass passwords against https://haveibeenpwned.com/Passwords
[](https://travis-ci.org/fopina/kdbxpasswordpwned)
[](https://coveralls.io/github/fopina/kdbxpasswordpwned?branch=master)
[](https://microbadger.com/images/fopina/kdbxpasswordpwned)
[](https://microbadger.com/images/fopina/kdbxpasswordpwned)
[](https://pypi.python.org/pypi/kdbxpasswordpwned)
[](https://pypi.python.org/pypi/kdbxpasswordpwned)
### Disclosure
Even if Troy Hunt's API does provide some sense of privacy (as we don't share the password nor even the full SHA1), always review the tools you use with your KeePass files (such as this script which is small and you can easily see the password is not sent anywhere except HIBP API). I have reviewed libkeepass code (0.3.0, pinned in requirements) which is also small, and, as PyPI does not allow replacing existing versions, it is safe.
Also be sure to install tools you trust from places you trust or you might end up installing some shady version such as [this fork](https://github.com/fopina/kdbxpasswordpwned/compare/master...SlivTaMere:bea0f5c) which sends the full password (not the hash) to a different endpoint.
### Usage
Install using `pip`
```bash
$ pip install kdbxpasswordpwned
Collecting kdbxpasswordpwned
Successfully installed kdbxpasswordpwned-0.3
```
And use the CLI
```bash
$ kdbxpasswordpwned -h
usage: kdbxpasswordpwned [-h] [-k KEYFILE] [-u] [-p] kdbx
positional arguments:
kdbx keepass file
optional arguments:
-h, --help show this help message and exit
-k KEYFILE, --keyfile KEYFILE
Keyfile if needed
-u, --show-user show username for found entries
-p, --show-password show password for found entries (high shoulders?)
```
```bash
$ kdbxpasswordpwned /path/to/test_assets/sample.kdbx
Password:
Password for title1 seen 1151 times before
Password for title2 seen 61164 times before
```
Or simply use the docker image
```bash
$ docker run --rm -ti \
-v /path/to/test_assets/sample_with_key.kdbx:/tmp.kdbx:ro \
-v /path/to/test_assets/sample.key:/tmp.key:ro \
fopina/kdbxpasswordpwned -upk /tmp.key /tmp.kdbx
Password for title1 seen 1151 times before - testuser - testit
Password for title2 seen 61164 times before - None - blabla
```
Metadata
Release files for kdbxpasswordpwned 0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| kdbxpasswordpwned-0.5.tar.gz | 3.4 kB | Without provenance | Details |
Release files / kdbxpasswordpwned-0.5.tar.gz
| Download URL | kdbxpasswordpwned-0.5.tar.gz |
|---|---|
| Size | 3.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
42535e7d4db9582db80ee89916dfb5082127bc129e16e02d6bcc767ed24e9697
|
|
BLAKE2b-256 checksum How to use checksums |
6875307ee3dc2da8cfe13130a7983a79b43ed4de9ee5a52eae21d4da842d7883
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.20.1 setuptools/40.7.0 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/2.7.14
|
Security for kdbxpasswordpwned 0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.