hashcat Forum
Stop auto incrementing - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Deprecated; Ancient Versions (https://hashcat.net/forum/forum-46.html)
+--- Forum: Very old oclHashcat-plus Support (https://hashcat.net/forum/forum-23.html)
+--- Thread: Stop auto incrementing (/thread-1533.html)

Pages: 1 2


Stop auto incrementing - radix - 09-05-2012

Not sure changed your mind to auto increment but it was the worst idea ever. Give us --increment back pls.


RE: Stop auto incrementing - Rolf - 09-05-2012

Rolf supports this idea!


RE: Stop auto incrementing - M@LIK - 09-05-2012

+1... I guess...


RE: Stop auto incrementing - blaz - 09-05-2012

i also support this


RE: Stop auto incrementing - james123 - 09-05-2012

+1 bitch


RE: Stop auto incrementing - epixoip - 09-05-2012

I can get behind this as well.


RE: Stop auto incrementing - atom - 09-05-2012

New users are irritated to much by a cracking-tool which is not doing using auto-increment per default and of course we want to make it as easy as possible for them to get into this not so easy program. Also, the experienced user still can use --bf-min N --bf-max N.


RE: Stop auto incrementing - Rolf - 09-05-2012

Yea, but what if you have 1k+ of masks, each of separate length ?
Max len approach sucks.
Either no default increment(like it was be4) or --no-increment would be the viable solution.


RE: Stop auto incrementing - radix - 09-05-2012

(09-05-2012, 11:21 AM)atom Wrote: New users are irritated to much by a cracking-tool which is not doing using auto-increment per default and of course we want to make it as easy as possible for them to get into this not so easy program. Also, the experienced user still can use --bf-min N --bf-max N.

So you will punish the people that are more seasoned in this area by requiring us to add extra opts? Thats kind of like a kick in the nuts.


RE: Stop auto incrementing - epixoip - 09-05-2012

(09-05-2012, 11:32 AM)Rolf Wrote: Yea, but what if you have 1k+ of masks, each of separate length ?
Max len approach sucks.
Either no default increment(like it was be4) or --no-increment would be the viable solution.

+1, That's exactly the problem. If I want to hit the top 200 masks from a dump, I can't just simply loop through the masks -- I'll end up with a lot of wasted effort. It can be worked around with an extra line in my loop and adding more switches, but I don't think it should be necessary to do so.