根据https://haveibeenpwned.com/passwords检查keepass密码
kdbxpasswordpwned的Python项目详细描述
#kdbxpasswordpwned
对照https://haveibeenpwned.com/passwords检查keepass密码
[![构建状态](https://travis-ci.org/fopina/kdbxpasswordpwned.svg?branch=master)(https://travis ci.org/fopina/kdbxpasswordpwned)
[![覆盖状态](https://coveralls.io/repos/github/fopina/kdbxpasswordpwned/badge.svg?branch=master)(https://coveralls.io/github/fopina/kdbxpasswordpwned?分支=主)
[![docker版本](https://images.microbadger.com/badges/version/fopina/kdbxpasswordpwned.svg)(https://microbadger.com/images/fopina/kdbxpasswordpwned)
[![Docker图片](https://images.microbadger.com/badges/image/fopina/kdbxpasswordpwned.svg)(https://microbadger.com/images/fopina/kdbxpasswordpwned)
[![PYPI版本](https://img.shields.io/pypi/v/kdbxpasswordpwned.svg)(https://pypi.python.org/pypi/kdbxpasswordpwned)
[![pypi python版本](https://img.shields.io/pypi/pyversions/kdbxpasswordpwned.svg)(https://pypi.python.org/pypi/kdbxpasswordpwned)
始终查看keepass文件使用的工具(例如这个脚本很小,您可以很容易地看到除了hibpi之外,密码不会发送到任何地方)。我已经回顾了LBeKePASS代码(0.3.0,在需求中被钉住),这也是小的,并且,由于PyPI不允许替换现有版本,它是安全的。
也要确保从您信任的地方安装您信任的工具,否则您可能会安装一些可疑的版本,例如[this fork](https://github.com/fopina/kdbxpasswordpwned/compare/master…slivtamere:bea0f5c),它会将完整密码(而不是散列)发送到不同的端点。
`
`` bash ``bash
$pip安装kdbxpasswordpwned
kdbxpassasswordpwned
kdbxpasswordpwned成功安装kdbxpasswordpwned-0.3
````
`` bash
`` bash
$kdbxpasswordpwned-h
用法:kdbxpasswordpwned[-h[-k keyfile][-u][-p]kdbx
/>posposition参数:
br/>kdbx keebx keebx keepwordpwned[-h-h[-h][-k keyfile-k-通过文件
BR/>可选参数:
-H,帮助显示此帮助消息并退出
-KEKFILE,-KEYFILE密钥文件
密钥文件(如果需要的话)BR/> -U,显示用户显示的用户名:BR/> -P,-显示已找到的密码(高肩)密码显示?
```
```bash
$kdbxpasswordpwned/path/to/test_assets/sample.kdbx
密码:
title1的密码在
title2的密码在
`````
/路径/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
title1的密码在-testuser-testit
title2的密码在-none-blabla
```
对照https://haveibeenpwned.com/passwords检查keepass密码
[![构建状态](https://travis-ci.org/fopina/kdbxpasswordpwned.svg?branch=master)(https://travis ci.org/fopina/kdbxpasswordpwned)
[![覆盖状态](https://coveralls.io/repos/github/fopina/kdbxpasswordpwned/badge.svg?branch=master)(https://coveralls.io/github/fopina/kdbxpasswordpwned?分支=主)
[![docker版本](https://images.microbadger.com/badges/version/fopina/kdbxpasswordpwned.svg)(https://microbadger.com/images/fopina/kdbxpasswordpwned)
[![Docker图片](https://images.microbadger.com/badges/image/fopina/kdbxpasswordpwned.svg)(https://microbadger.com/images/fopina/kdbxpasswordpwned)
[![PYPI版本](https://img.shields.io/pypi/v/kdbxpasswordpwned.svg)(https://pypi.python.org/pypi/kdbxpasswordpwned)
[![pypi python版本](https://img.shields.io/pypi/pyversions/kdbxpasswordpwned.svg)(https://pypi.python.org/pypi/kdbxpasswordpwned)
始终查看keepass文件使用的工具(例如这个脚本很小,您可以很容易地看到除了hibpi之外,密码不会发送到任何地方)。我已经回顾了LBeKePASS代码(0.3.0,在需求中被钉住),这也是小的,并且,由于PyPI不允许替换现有版本,它是安全的。
也要确保从您信任的地方安装您信任的工具,否则您可能会安装一些可疑的版本,例如[this fork](https://github.com/fopina/kdbxpasswordpwned/compare/master…slivtamere:bea0f5c),它会将完整密码(而不是散列)发送到不同的端点。
`
`` bash ``bash
$pip安装kdbxpasswordpwned
kdbxpassasswordpwned
kdbxpasswordpwned成功安装kdbxpasswordpwned-0.3
````
`` bash
`` bash
$kdbxpasswordpwned-h
用法:kdbxpasswordpwned[-h[-k keyfile][-u][-p]kdbx
/>posposition参数:
br/>kdbx keebx keebx keepwordpwned[-h-h[-h][-k keyfile-k-通过文件
BR/>可选参数:
-H,帮助显示此帮助消息并退出
-KEKFILE,-KEYFILE密钥文件
密钥文件(如果需要的话)BR/> -U,显示用户显示的用户名:BR/> -P,-显示已找到的密码(高肩)密码显示?
```
```bash
$kdbxpasswordpwned/path/to/test_assets/sample.kdbx
密码:
title1的密码在
title2的密码在
`````
/路径/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
title1的密码在-testuser-testit
title2的密码在-none-blabla
```