From d82c6ca962dd807c3f53d8b272e2c4ce663f555c Mon Sep 17 00:00:00 2001 From: koksnuss Date: Sun, 12 May 2019 15:04:49 +0200 Subject: [PATCH] Enhance wording --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index cdbc509..87039f6 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ This tools searches your password in the leak-database from [haveibeenpwned.com] # Examples -## Pass passwords as arguments +## Check multiple password at once as script arguments Note: This approach will put all entered password in your shell command history (such as the bash history). Therefore this method is only recommended if you trust anybody else who has acces to the history or if you clean all passwords from the history. The following shows that passwords like `password`, `p@ssw0rd` and even `p@$$wOrd` have been leaked already and should obviously never be used as passwords again. Note the use of single ticks `'` for the third and fourth password as the `$`-sign confuses the shell otherwise. @@ -28,7 +28,7 @@ P@$sW0rD& not yet 1B34EF732FC1EB5925EEAF3155BECBB44275194A ``` -## Enter password secretly into a prompt +## Check one password at a time via a secure prompt When you invoke the script without any arguments you will be prompted for a password which you can enter without somebody else seeing the characters on the screen: ``` ./have_I_b33n_pwned.py