Description: fix wrong information or typos in the help and README file
Author: Joao Eriberto Mota Filho <eriberto@debian.org>
Last-Update: 2015-07-24
Index: hashrat-1.6.1/README
===================================================================
--- hashrat-1.6.1.orig/README
+++ hashrat-1.6.1/README
@@ -99,7 +99,7 @@ Options:
   -cgi            Run in HTTP CGI mode
   -net            Treat 'file' arguments as either ssh or http URLs, and pull files over the network and then hash them (Allows hashing of files on remote machines).
                   URLs are in the format ssh://[username]:[password]@[host]:[port] or http://[username]:[password]@[host]:[port]..
-  -idfile <path>  Path to an ssh private key file to use to authenticate INSTEAD OF A PASSWORD when pulling files via ssh.
+  -idfile <path>  Path to a ssh private key file to use to authenticate INSTEAD OF A PASSWORD when pulling files via ssh.
   -xattr          Use eXtended file ATTRibutes. In hash mode, store hashes in the file attributes, in check mode compare against hashes stored in file attributes.
   -txattr         Use TRUSTED eXtended file ATTRibutes. In hash mode, store hashes in 'trusted' file attributes. 'trusted' attributes can only be read and written by root.
   -attrs          comma-separated list of filesystem attribute names to be set to the value of the hash.
@@ -129,7 +129,7 @@ USE EXAMPLES:
 
 	hashrat
 
-		Generate an md5 hash of data read from stdin  (default hash type is md5).
+		Generate a md5 hash of data read from stdin  (default hash type is md5).
 
 	hashrat -jh256
 
@@ -137,7 +137,7 @@ USE EXAMPLES:
 		
 	hashrat -sha256 -64
 
-		Generate an sha-256 hash of data read from stdin, output with base64 encoding.
+		Generate a sha-256 hash of data read from stdin, output with base64 encoding.
 
 	hashrat -sha256 -64 -lines
 
@@ -145,7 +145,7 @@ USE EXAMPLES:
 
 	hashrat -md5 -trad -rawlines
 
-		Read lines from stdin, and generate an md5 hash in 'traditional' format for every line INCLUDING TRAILING WHITESPACE. This is compatible with 'echo text | md5sum' where 'text' is one line, as 'echo' adds a newline to the end of the text it outputs.
+		Read lines from stdin, and generate a md5 hash in 'traditional' format for every line INCLUDING TRAILING WHITESPACE. This is compatible with 'echo text | md5sum' where 'text' is one line, as 'echo' adds a newline to the end of the text it outputs.
 
 	hashrat *
 
@@ -208,7 +208,7 @@ USES FOR HASHRAT
 
 		echo "facebook.com password 1234" | hashrat -sha1 -64
 
-	Obviously, my password isn't 'password' and my pin isn't '1234', but you get the idea. This gives me a 28-character string that should take "8.02 trillion trillion centuries" to crack with a "massive cracking array" according to Steve Gibson's 'Password haystacks' utility, https://www.grc.com/haystack.htm. This is what I then use as my password. Unfortunately some websites won't take a 28-character password, and for these I have to truncate to the appropriate length (using the -n flag), but the results are still stronger than anything I could remember, and nothing needs storing on disk (as with password managers). 
+	Obviously, my password isn't 'password' and my pin isn't '1234', but you get the idea. This gives me a 28-character string that should take "8.02 trillion centuries" to crack with a "massive cracking array" according to Steve Gibson's 'Password haystacks' utility, https://www.grc.com/haystack.htm. This is what I then use as my password. Unfortunately some websites won't take a 28-character password, and for these I have to truncate to the appropriate length (using the -n flag), but the results are still stronger than anything I could remember, and nothing needs storing on disk (as with password managers). 
 
 	There are some dangers to using the 'echo' method shown above if you are on a shared machine, or if someone gets hold of your computer/harddrive. On a shared machine someone could type 'ps ax' to see all commands running, and if they time it right, they might see your command-line with your password in it. Another danger lies in using a shell (like bash) that will record your typed commands so you can recall them later. Bash stores this information on disk in the file .bash_history, so if you use the 'echo' method shown above your password will be saved on disk. To combat this hashrat has 'line mode'
 
Index: hashrat-1.6.1/command-line-args.c
===================================================================
--- hashrat-1.6.1.orig/command-line-args.c
+++ hashrat-1.6.1/command-line-args.c
@@ -513,7 +513,7 @@ printf("  %-15s %s\n","-rl", "Read lines
 printf("  %-15s %s\n","-cgi", "Run in HTTP CGI mode");
 printf("  %-15s %s\n","-net", "Treat 'file' arguments as either ssh or http URLs, and pull files over the network and then hash them (Allows hashing of files on remote machines).");
 printf("  %-15s %s\n","", "URLs are in the format ssh://[username]:[password]@[host]:[port] or http://[username]:[password]@[host]:[port]..");
-printf("  %-15s %s\n","-idfile <path>", "Path to an ssh private key file to use to authenticate INSTEAD OF A PASSWORD when pulling files via ssh.");
+printf("  %-15s %s\n","-idfile <path>", "Path to a ssh private key file to use to authenticate INSTEAD OF A PASSWORD when pulling files via ssh.");
 printf("  %-15s %s\n","-xattr", "Use eXtended file ATTRibutes. In hash mode, store hashes in the file attributes, in check mode compare against hashes stored in file attributes.");
 printf("  %-15s %s\n","-txattr", "Use TRUSTED eXtended file ATTRibutes. In hash mode, store hashes in 'trusted' file attributes. 'trusted' attributes can only be read and written by root.");
 printf("  %-15s %s\n","-attrs", "comma-separated list of filesystem attribute names to be set to the value of the hash.");
