vanhauser-thc/thc-hydra

xHydra additionnal arguments

Open

#901 opened on Oct 20, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (1,913 forks)batch import
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (8,689 stars)
PR merge metrics
 (Avg merge 2d 14h) (2 merged PRs in 30d)

Description

Hi,

I use Hydra and most of the time xHydra (GUI) because it's easier/faster ! I love it... But sometime I need to switch to command line with Hydra because some arguments are not capable to be set like:

hydra -v -l yourname -p yourpass -t 16 -F 192.168.1.1 rdp

A great warning is displayed telling:

[WARNING] rdp servers often don't like many connections, use -t 1 or -t 4 to reduce the number of parallel connections and -W 1 or -W 3 to wait between connection to allow the server to recover

Nice, I can easly set the amount of parallel connections via "Number of tasks" value... But I observe the "Wait (-W)" argument is not available in the GUI fields.

Then, my request is :

  • May be add the "Wait time between each attempt" field to solve this specific option
  • Or may be, simply add in the tuning section a "extra manual argument" field to allow us to set all special, missing, newer arguments !

Regards

Contributor guide

Research direction
Locate the xHydra source code (likely in the 'xhydra' subdirectory). Find the GUI form for setting Hydra arguments (e.g., the 'Number of tasks' field). Add a new input field for the ' W' (wait time) argument or a generic 'extra arguments' text field. Ensure the new field value is passed to the Hydra command line when starting an attack. Test the changes with a simple Hydra command.
Tech stack
c
Domain
security
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75