*2john tools should warn users when they produce particularly revealing "hashes"
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Similarly to #3130, other *2john tools should also be enhanced to warn users when the resulting "hashes" contain entire private keys (for cryptocoin wallets) or embed entire encrypted archives or filesystems (with the user's actual data in there).
The first task here, also relevant to #3139, is to enumerate such tools/formats in a comment here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by enumerating the *2john tools and formats that can expose private keys or embed encrypted archives or filesystems, as requested in the issue and related issues #3130 and #3139. Done means documenting the affected tools and formats clearly enough to define which outputs need user warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100