Skip to content
New issue

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

RAR formats: Reject old archives #5275

Merged
merged 1 commit into from
Apr 12, 2023

Conversation

magnumripper
Copy link
Member

@magnumripper magnumripper commented Apr 11, 2023

These have "unknown" KDF and encryption, and no salt. We could work it out by examining public unrar source code, but such archives are so rare I'm not sure we'll ever bother.

Closes #5271 - see also #5273

These have "unknown" KDF and encryption, and no salt. We could work it out
by examining public unrar source code, but such archives are so rare I'm
not sure we'll ever bother.

Closes openwall#5271
@magnumripper magnumripper merged commit a388e50 into openwall:bleeding-jumbo Apr 12, 2023
@magnumripper magnumripper deleted the oldrar branch April 12, 2023 08:42
@solardiz
Copy link
Member

Should we ideally also do such rejection in the format? For "hashes" generated by rar2john from prior to this PR.

@magnumripper
Copy link
Member Author

Should we ideally also do such rejection in the format? For "hashes" generated by rar2john from prior to this PR.

I added that at first but rejected it. The only thing the formats can detect is an all-zero salt and I'm not sure that could not happen (and be valid) in some other remote cases. The formats could/should emit a warning about it though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RAR3-p hash with *35 ending won't find password in wordlist
2 participants