Commit 26713537 by Cedric Tissieres

Merge branch 'master' into 'master'

Account for Hyper-threading in core count instructions

See merge request !1
parents 2a71c371 8ef820a7
......@@ -55,7 +55,8 @@ Ophcrack rainbow tables are available at ophcrack rainbow tables page
This step is optional but will speed up the cracking process.
Run ophcrack and set the number of threads under the Preferences tab to the
number of cores of the computer running ophcrack.
number of logical cores of the computer running ophcrack (accounting for
Hyper-threading).
### Second step ###
......
......@@ -13,7 +13,7 @@
<H2 id="pref">Preferences</H2><p>
<ul>
<li>Number of threads: It allows you to set the number of threads the program will use and to enable or disable the brute force cracking. The number of threads should be set to the number of cores of the computer running ophcrack plus one. For example, for an old processor set the number of threads to 2, for a Core 2 Duo to 3 and for a Core 2 Quad to 5. If you change this value, you have to exit ophcrack and to restart it in order to save the change. If you don't exit and restart, the new number of threads will not be taken into account by the program.
<li>Number of threads: It allows you to set the number of threads the program will use and to enable or disable the brute force cracking. The number of threads should be set to the number of logical cores of the computer running ophcrack (accounting for Hyper-threading). For example, for an old processor set the number of threads to 1, for a Core 2 Duo to 2 and for a Core 2 Quad to 4. If you change this value, you have to exit ophcrack and to restart it in order to save the change. If you don't exit and restart, the new number of threads will not be taken into account by the program.
<li>Number of hash/redux per task: Every work that ophcrack does is separated in smaller tasks. This setting enables you to specify the length of one task. Depending on your hardware, using a smaller or larger value can enhance performances a little bit.
<li>Max length of the disk queue: In order to reduce the I/O impact on performance, ophcrack precomputes more tasks than what the harddisk can handle normally (when tables are not loaded in RAM). Setting this value to 50 will make ophcrack wait more on the harddisk. You should usually let it to 500.
<li>Bruteforce: ophcrack cracks the hashes loaded using brute force up to 4 characters if this setting is enabled. It permits one to speed up the cracking process since small passwords won't be searched in rainbow tables but bruteforced. The bruteforce is executed at the same time as the preloading.
......
......@@ -14,7 +14,7 @@ Ophcrack rainbow tables are avaible at ophcrack rainbow tables page (http://ophc
This step is <strong>optional</strong> but will speed up the cracking process.
<br>
<br>
Run ophcrack and set the number of threads under the Preferences tab to the number of cores of the computer running ophcrack plus one.For example, for an old processor set the number of threads to 2, for a Core 2 Duo to 3 and for a Core 2 Quad to 5. If you change this value, you have to exit ophcrack and to restart it in order to save the change. If you don't exit and restart, the new number of threads will not be taken into account by the program.
Run ophcrack and set the number of threads under the Preferences tab to the number of logical cores of the computer running ophcrack (accounting for Hyper-threading). For example, for an old processor set the number of threads to 1, for a Core 2 Duo to 2 and for a Core 2 Quad to 4. If you change this value, you have to exit ophcrack and to restart it in order to save the change. If you don't exit and restart, the new number of threads will not be taken into account by the program.
</p>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment