Hopefully, the results of it will be useful for others.įor a quick comparison of Medusa, Ncrack, and THC-Hydra see: medusa-compare.html Writing this application was a trainingĮxercise for me. I am not an experienced C programmer, nor do I consider myself anĮxpert in multi-threaded programming. Medusa is pthread-based and does not unnecessarily duplicate information. When testing many hosts/users at once thisĬreates a large amount of overhead as user/password lists must be duplicated for each forked Hydra accomplishes its parallel testing by forking off a new process forĮach host and instance of the service being tested.

The start to support parallel testing of hosts, users and passwords. Hydra not being designed from the ground-up to support this.

This was mainly due to my coding ignorance, but was probably also due to Retro-fitting the parallel host code to Hydra was a serious A while back I added several features to Hydra (parallel host Than fix Hydra, I decided to create my own buggy application which could crash in Was no longer confident that Hydra was actually doing what it claimed to be. Maybe I'm just lame, but Hydra frequently crashed on me. Why create Medusa? Isn't this the same thing as THC-Hydra? Here are some That no modifications are necessary to the core application in order to extend the supported list Each service module exists as an independent. Additionally, a combination file format allows the user For example, each item can be either a single entry or a fileĬontaining multiple entries. Target information (host/user/password) can be specified inĪ variety of ways. Brute-force testing can be performed against multiple The author considers following items as some of the key features of this The goal is to support as many services which allow remote authentication as Medusa is intended to be a speedy, massively parallel, modular, login brute-forcer. Foofus Networking Services - Medusa Medusa Parallel Network Login Auditor JoMo-Kun / jmk 'AT' foofus 'DOT' net

Thc hydra shh too slow