| 1 |
Source: medusa |
| 2 |
Section: admin |
| 3 |
Priority: optional |
| 4 |
Maintainer: Debian Security Tools <[email protected]> |
| 5 |
Uploaders: Adrian Alves <[email protected]>, |
| 6 |
Matheus Polkorny <[email protected]> |
| 7 |
Build-Depends: debhelper-compat (= 13), |
| 8 |
libssl-dev, |
| 9 |
libsvn-dev, |
| 10 |
libpq-dev, |
| 11 |
libssh2-1-dev, |
| 12 |
libgcrypt-dev, |
| 13 |
libsmb2-dev [!hurd-any], |
| 14 |
freerdp3-dev [!hurd-any !m68k], |
| 15 |
Standards-Version: 4.7.2 |
| 16 |
Homepage: http://foofus.net/?page_id=51 |
| 17 |
Vcs-Git: https://salsa.debian.org/pkg-security-team/medusa.git |
| 18 |
Vcs-Browser: https://salsa.debian.org/pkg-security-team/medusa |
| 19 |
|
| 20 |
Package: medusa |
| 21 |
Architecture: any |
| 22 |
Depends: ${shlibs:Depends}, ${misc:Depends} |
| 23 |
Description: fast, parallel, modular, login brute-forcer for network services |
| 24 |
Medusa is intended to be a speedy, massively parallel, modular, login |
| 25 |
brute-forcer. The goal is to support as many services which allow remote |
| 26 |
authentication as possible. The author considers following items as some of |
| 27 |
the key features of this application: |
| 28 |
* Thread-based parallel testing. Brute-force testing can be |
| 29 |
performed against multiple hosts, users or passwords |
| 30 |
concurrently. |
| 31 |
* Flexible user input. Target information (host/user/password) can |
| 32 |
be specified in a variety of ways. For example, each item can be |
| 33 |
either a single entry or a file containing multiple entries. |
| 34 |
Additionally, a combination file format allows the user to |
| 35 |
refine their target listing. |
| 36 |
* Modular design. Each service module exists as an |
| 37 |
independent .mod file. This means that no modifications are |
| 38 |
necessary to the core application in order to extend the |
| 39 |
supported list of services for brute-forcing. |