Skip to content

Commit

Permalink
readme updates
Browse files Browse the repository at this point in the history
  • Loading branch information
vanhauser-thc committed Feb 6, 2016
1 parent 99f2e99 commit 1415b72
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 5 deletions.
2 changes: 1 addition & 1 deletion README
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

H Y D R A

(c) 2001-2014 by van Hauser / THC
(c) 2001-2016 by van Hauser / THC
<[email protected]> http://www.thc.org
many modules were written by David (dot) Maciejak @ gmail (dot) com
BFG code by Jan Dlabal <[email protected]>
Expand Down
15 changes: 11 additions & 4 deletions web/README
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@

H Y D R A

(c) 2001-2014 by van Hauser / THC
(c) 2001-2016 by van Hauser / THC
<[email protected]> http://www.thc.org
co-maintained by David (dot) Maciejak @ gmail (dot) com
many modules were written by David (dot) Maciejak @ gmail (dot) com
BFG code by Jan Dlabal <[email protected]>

Licensed under AGPLv3 (see LICENSE file)
Expand Down Expand Up @@ -119,7 +119,7 @@ Via the command line options you specify which logins to try, which passwords,
if SSL should be used, how many parallel tasks to use for attacking, etc.

PROTOCOL is the protocol you want to use for attacking, e.g. ftp, smtp,
http-get or many others are vailable
http-get or many others are available
TARGET is the target you want to attack
OPTIONS are optional values which are special per PROTOCOL module

Expand Down Expand Up @@ -164,6 +164,14 @@ target entry in the file, e.g.:
127.0.0.1
127.0.0.1:2121

Note that if you want to attach IPv6 targets, you must supply the -6 option
and *must* put IPv6 addresses in brackets in the file(!) like this:
foo.bar.com
target.com:21
[fe80::1%eth0]
[2001::1]
[2002::2]:8080
[2a01:24a:133:0:00:123:ff:1a]


LOGINS AND PASSWORDS
Expand Down Expand Up @@ -321,7 +329,6 @@ BUGS & FEATURES
Hydra:
Email me or David if you find bugs or if you have written a new module.
[email protected] (and put "antispam" in the subject line)
David (dot) Maciejak @ gmail (dot) com


You should use PGP to encrypt emails to [email protected] :
Expand Down

0 comments on commit 1415b72

Please sign in to comment.