how to make an attack
Prompt, please how to convey expressions hashcat:
[font=Arial, Helvetica, sans-serif]example:[/font]
[font=Arial, Helvetica, sans-serif]word1 word2[/font]
[font=Arial, Helvetica, sans-serif]word1_word2[/font]
[font=Arial, Helvetica, sans-serif]word1-word2[/font]
[font=Arial, Helvetica, sans-serif]-word1word2[/font]
[font=Arial, Helvetica, sans-serif]word1word2-[/font]
[font=Arial, Helvetica, sans-serif]=word1word2[/font]
[font=Arial, Helvetica, sans-serif]word1word2&[/font]
[font=Arial, Helvetica, sans-serif]....[/font]
[font=Arial, Helvetica, sans-serif]...[/font]
(06-24-2019, 12:26 AM)epixoip Wrote:
Thank You!
(06-24-2019, 12:26 AM)epixoip Wrote:
With the key -k works, with the key -j - no. See screenshot. Can you tell me where I'm wrong?

Attached Files
.jpg   Screenshot_1.jpg (Size: 95.91 KB / Downloads: 9)
.jpg   Screenshot_2.jpg (Size: 143.41 KB / Downloads: 7)
probably just an escaping problem. for instance use "$-" instead on some operating system, some need \$- etc.

I would test with a rule that doesn't need escaping at all, like:
hashcat -j u ...

I think in your case it makes sense to have dicts where the special characters and numbers are already appended and/or prepended and combine them during the actual attack/cracking.

hashcat --stdout -a 6 -1 ?d?s -o dict.txt raw_wordlist.txt ?1
hashcat --stdout -a 7 -1 ?d?s -o dict.txt ?1 raw_wordlist.txt

hashcat -m 0 -w 3 -O -a 1 hashes.txt dict.txt dict.txt

to optimize things you could also optimize the --custom-charset1 (or short -1) to only contain the chars that are for sure needed (maybe not every character in ?s is allowed in your case) and also make 2 dicts instead of only one "dict.txt" and both sides are more optimized (but it's also a little bit more work for you and might not be worthwhile depending on how fast the hashing algorithm you need is, I see -m 0 in your command line which is of course a very fast algo)

of course the rule-based attack is nice too, but the problem is that -j/-k do not allow rule *files*, only single rules are accepted, so you would need to launch hashcat for each and every new rule (and rule combination, if you use -j AND -k)