GPG2John failing with GnuPGs .key format
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce
Take a .key file from GnuPGs AppData\Roaming\gnupg\private-keys-v1.d that has a password protected private key and try to extract a hash with gpg2john for cracking the forgotten password.
can't find PGP armor boundary.
System configuration
Attach details about your OS and about JtR, including:
Version: 1.9.0-jumbo-1 Build: cygwin 64-bit x86_64 AVX2 AC OMP
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 with the gpg2john entry point and reproduce the failure using a password-protected .key file from GnuPG's private-keys-v1.d directory. Check how this format is handled when the tool reports "can't find PGP armor boundary"; done means the file produces a crackable hash instead of that error.
Written by the indexing model from the issue text.
Assessment
- Domain
- cryptography, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100