Operational efficiency issues and support username: hash
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 238
- PR merge metrics
- No merged PRs in 30d
Description
Why? When i Using the "gocrack" BUT it's significantly less efficient than The "hashcat".
Is my gocrack-configuration's question?
THX! That's my runing logs:
--------------------------------**using hashcat** --------------------------------------
Session ..........: hashcat
Status ...........: Exhausted
Hash.Type ........: MD5
Hash.Target ......: onlypass.txt
Time.Started .....: Mon Nov 6 15:36:34 2017 (2 mins, 10 secs)
Time.Estimated ...: Mon Nov 6 15:38:44 2017 (0 secs)
Guess.Base .......: File (onlydic.txt)
Guess.Queue ......: 1/1 (100.00%)
Speed.Dev. # 1 .....: 475.8 kH / s (7.84 ms)
Recovered ........: 3851155/8396914 (45.86%) Digests, 0/1 (0.00%) Salts
Recovered / Time ...: CUR: 2408655, N / A, N / A AVG: 1785572, 107134366, -2147483648 (Min, Hour, Day)
Progress .........: 56932171/56932171 (100.00%)
Rejected .........: 0/56932171 (0.00%)
Restore.Point ....: 56932171/56932171 (100.00%)
Candidates. # 1 ....: midas1342 -> drdjcgv
HWMon.Dev. # 1 .....: Temp: 33c Fan: 46% Util: 20% Core: 1139MHz Mem: 3304MHz Bus: 1
-------------------------------- **using gocrack** --------------------------------------
Time Started Mon Nov 6 14:50:50 2017
Time Estimated Mon Nov 6 22:05:24 2017 (6 hours, 32 mins)
In addition, hashcat uses the --username option to identify user and hash combinations like admin: e10adc3949ba59abbe56e057f20f883e.
gocrack how to support such a format?
Translate for Google
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported GoCrack and hashcat logs, then compare the configured cracking workflow and command invocation. Check how GoCrack handles hashcat inputs and whether it can accept username:hash values like admin:e10adc3949ba59abbe56e057f20f883e. Done means the requested format is supported and the efficiency difference is explained or addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100