[BUG] When resuming a session, finished tries count towards new session tries - messing up ETA · vanhauser-thc/thc-hydra#824

(0 留言) (0 反應) (0 負責人)C (8,689 star) (1,913 fork)batch import

best practicegood first issuehelp wanted

描述

I left a session running for about 10 minutes during which ~9000 tries were done. Then I remebered to add -f option so I stopped the execution and resumed it using -R with the added option. Now after 1 minute I get: [STATUS] 10166.00 tries/min, 10166 tries in 00:01h, 989834 to do in 01:38h, 32 active even though the actual speed is somewhere around(from the previous session): [STATUS] 634.00 tries/min, 634 tries in 00:01h, 999366 to do in 26:17h, 32 active

With time due to averaging it does converge towards the actual speed but I believe this is undesired.

貢獻者指南

技術棧: c
領域: backendsecurity
議題類型: bug
難度: 4
預計時間: 1-2 days
活動狀態: fresh
清晰度: mostly clear
前置要求: C programminghydra session system
新手友善度: 35
研究方向: Investigate the session resume logic in thc hydra, likely in the main source files such as hydra session.c or hydra core.c. The bug seems to be that the finished tries from a previous session are not reset or excluded when resuming with new options, causing the ETA calculation to use inflated try counts. Look for how the 'tries' counter is initialized on resume and how the statistics module accumulates data over time. The fix might involve resetting the finished tries counter or properly adjusting the ETA calculation to consider only new tries.