crunch 2.4

Quote:

---

Originally Posted by bofh28

Running crunch outside of X should be the fastest way to run crunch. I don't have the time to test right now but I will add it to the todo list.

---

The > /dev/null is the killer. Inside a terminal, if I'm reading between the lines correctly, the individual in question is running into a purely display-buffer bottleneck, in much the same way one would find a slower crunch time onto a 5400rpm disk vs a 7200rpm disk. The only reason the software itself should run slow is pure CPU cycles, until you start either writing it to stdout/stderr, or to a disk/network. Inbuilt cracking should be fine, but generating any kind of visual list would slow things down significantly.

I could be firing from the left field though, in which case write it off as a bit of random knowledge transferred ;)

Quote:

---

Originally Posted by Gitsnik

The > /dev/null is the killer. Inside a terminal, if I'm reading between the lines correctly, the individual in question is running into a purely display-buffer bottleneck, in much the same way one would find a slower crunch time onto a 5400rpm disk vs a 7200rpm

---

Actually the display buffer bottleneck is exactly the issue I was thinking of when I posted the >/dev/null to eliminate that bottleneck. I ran into the buffer bottleneck several times when I was benchmarking crunch. I now use -o for benchmarking. Yeah I am IO bound now but I do have 7200rpm SCSI disks. However I am just making sure that I don't slow down crunch too much from the original version.

How do I install this after download? (just switched from Windows to Linux)

People like to see the progress of file crunching, an ooh ahh thing I guess.

Maybe writing to display less of the available info may reduce the bottleneck and help to improve performance.

I won't be adding a progress bar because:
1) writing to display takes time, granted a small amount of time but still
2) they is no way to estimate how long a task will take
3) People can open a second terminal window and do a ls to see what has been done

I just do a:
time ./crunch 1 5
to test for bottlenecks
of course this should be done outside X and preferable in single user mode

Great tool, If i want to creat a wordlist with following word "BiscottE" what is the easy and fast way? :confused:
The first and the last letter is upercase.
Thanks

For bofh28

Suggestion

Hi, i was a windows user and recently moved to Linux and became a big fan.
In relation to backtrack and the tools available as crunch i think is an excellent
work. HAIL to the creators and developers.
About crunch if I may, whant to submit an idea to you create a symbol just for upercase letters.
eg . /crunch 8 8 mixalpha -t §@@@@@@§


@ = Lowercase
§ = Upercase

Quote:

---

Originally Posted by MotherRuss1a

For bofh28

Suggestion

Hi, i was a windows user and recently moved to Linux and became a big fan.
In relation to backtrack and the tools available as crunch i think is an excellent
work. HAIL to the creators and developers.
About crunch if I may, whant to submit an idea to you create a symbol just for upercase letters.
eg . /crunch 8 8 mixalpha -t §@@@@@@§


@ = Lowercase
§ = Upercase

---

Crunch 2.5 has a uppercase symbol. I haven't released 2.5 yet as I have to get some code to work and I haven't had much time for crunch lately.

Quote:

---

Originally Posted by JellyBelly

People like to see the progress of file crunching, an ooh ahh thing I guess.

Maybe writing to display less of the available info may reduce the bottleneck and help to improve performance.

---

I thought it over and I think I might do what john does. If you press the space bar you see what is being generated. If I can figure out how to calculate the number of possible combinations or permutations there will be I could print something like:
output: wxyz 2345 of 30406

This won't be in 2.5 maybe 2.6.