We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[peng@pengArch assets]$ file hook.7z hook.7z: 7-zip archive data, version 0.4 [peng@pengArch assets]$ rarcrack --type 7z --threads 12 hook.7z RarCrack! 0.2 by David Zoltan Kedves ([email protected])
INFO: the specified archive type: 7z INFO: cracking hook.7z, status file: hook.7z.xml GOOD: password cracked: '9' GOOD: password cracked: '8' GOOD: password cracked: '1' GOOD: password cracked: '4' GOOD: password cracked: 'a' GOOD: password cracked: '5' GOOD: password cracked: 'b' GOOD: password cracked: '7' GOOD: password cracked: '6' GOOD: password cracked: '0' GOOD: password cracked: '3' GOOD: password cracked: '2' ver 0.2 is ok ver 0.4 is fail
The text was updated successfully, but these errors were encountered:
So version 0.2 of .7z files work? but not 0.4?
.7z
Also does it have to do with threading? What does rarcrack --type 7z hook.7z output?
rarcrack --type 7z hook.7z
Sorry, something went wrong.
No branches or pull requests
[peng@pengArch assets]$ file hook.7z
hook.7z: 7-zip archive data, version 0.4
[peng@pengArch assets]$ rarcrack --type 7z --threads 12 hook.7z
RarCrack! 0.2 by David Zoltan Kedves ([email protected])
INFO: the specified archive type: 7z
INFO: cracking hook.7z, status file: hook.7z.xml
GOOD: password cracked: '9'
GOOD: password cracked: '8'
GOOD: password cracked: '1'
GOOD: password cracked: '4'
GOOD: password cracked: 'a'
GOOD: password cracked: '5'
GOOD: password cracked: 'b'
GOOD: password cracked: '7'
GOOD: password cracked: '6'
GOOD: password cracked: '0'
GOOD: password cracked: '3'
GOOD: password cracked: '2'
ver 0.2 is ok
ver 0.4 is fail
The text was updated successfully, but these errors were encountered: