openwall / openwall/john

Add a benchmark_length flag for "benchmark all different costs"

Open
#5,601 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

https://github.com/openwall/john/issues/5315#issuecomment-1561732011
I'm also pondering a new flag (eg. 0x800) for benchmark_length, meaning "benchmark all different costs [that we have test vectors for] separately" (only considering first cost, for a start).

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 by reading the referenced comment in issue #5315 and trace where the benchmark_length option and available test vectors are handled. Determine the scope of supporting a new flag that benchmarks each known cost separately, initially considering only the first cost; done means the requested benchmark behavior works for the available vectors.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.