sha256crypt-ztex#3374
Conversation
solardiz
left a comment
There was a problem hiding this comment.
I've made some comments on improving the documentation, which should be done with separate commits/PR. I'll merge this now, then test this PR's new functionality after merging.
| | | / \ / | ||
| | process_bytes | / "main" \ <------ | ||
| | |<--+--| memory | | ||
| +---------------+ | \ (16x256b) / <------ |
There was a problem hiding this comment.
Should be 6x128B. BTW, let's use "B" for bytes if we use "b" for bits (ditto for the sha512crypt-ztex README). These documentation issues can be fixed in a separate commit and PR for both sha256crypt-ztex and sha512crypt-ztex.
| | procb_buf | -->| C.P.U. | | | ||
| +-----------+ | +-----------------------+ | | | ||
| ^ | | integer ops. incl. | | | | ||
| \ | | 6 x 16 registers(x16b)| | | |
There was a problem hiding this comment.
Here's where we use "b" for bits, and that's OK.
|
|
||
| - Each FPGA has 25 computing units, that's 75 cores, 150 keys are | ||
| computed in parallel. | ||
|
|
There was a problem hiding this comment.
It would be helpful to add (with the separate commit/PR) some info on relative resource usage by SHA-256 cores vs. the "overhead" (CPUs, glue logic). We do have this info in sha512crypt-ztex's README.
|
|
||
| [ZTEX:sha256crypt] | ||
| # Design tools reported possible frequency is 166.3 but tested boards | ||
| # miss guesses, often fail unless frequency is decreased. |
There was a problem hiding this comment.
It'd be helpful to add a similar comment for sha512crypt and Drupal7, stating those formats' design tools' reported frequency.
| Frequency = 135 | ||
| #TargetRounds = 1000000 | ||
|
|
||
|
|
There was a problem hiding this comment.
Thank you!
The documentation definitely requires an update / correction. I'm preparing a PR to include topics you've commented on. Maybe some other items require more detailed description, such as resource usage, performance of 16-bit CPU in sha256crypt-ztex vs 32-bit CPU in sha512crypt-ztex.
Regarding extra linefeed in run/john.conf:L386, I was unsure on style in john.conf. Sometimes sections that refer to different subsystems are separated with 2 empty lines, i.e. L419, L474.
There was a problem hiding this comment.
You're right about the extra linefeed, I missed the fact this was the very last ZTEX entry, and is followed by OpenCL stuff. Makes sense.
sha256crypt-ztex
often (timeout) and lose successful guesses. Default frequency is set to 135.