openwall / openwall/john

ZTEX: document "--fork"

Open
#4,283 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
C
Stars
13.6k
Forks
2.6k
PR merge metrics
No merged PRs in 30d

Description

Document the introduction of --fork support for ZTEX formats (#4027) in README-ZTEX (including when and how to use it, and when not to).

Mention in README-ZTEX that the way --fork sometimes speeds things up is through asynchronous USB transfers by the forked processes (so that while some transfer others may compute), which puts more pressure on the USB subsystem (as sometimes multiple processes will transfer concurrently) and thus might result in more frequent USB communication errors (exposing hardware, driver, and libusb issues), especially at high forked process counts.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with README-ZTEX and issue #4027 to understand the existing --fork support. Update the README to explain when and how to use --fork, when not to use it, and how asynchronous USB transfers can increase USB communication errors, especially with many forked processes. Done means all requested usage and USB caveats are documented.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.