-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add OpenCL support for cracking KeePass files #2471
Labels
Comments
I intend to look into this soon. |
a666e7e was a start |
magnumripper
added a commit
that referenced
this issue
Jan 30, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( This kernel should be rewritten as a looped kernel. See #2471.
magnumripper
added a commit
that referenced
this issue
Jan 30, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( This kernel should be rewritten as a looped kernel. See #2471.
magnumripper
added a commit
that referenced
this issue
Jan 30, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 30, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 30, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
Dang, many moving parts here. Maybe it's all set now. |
magnumripper
added a commit
that referenced
this issue
Jan 30, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 30, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 30, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 30, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 31, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 31, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 31, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 31, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Jan 31, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes :-( Closes #2471.
magnumripper
added a commit
that referenced
this issue
Feb 1, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes. Closes #2471.
magnumripper
added a commit
that referenced
this issue
Feb 1, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes. Closes #2471.
magnumripper
added a commit
that referenced
this issue
Feb 1, 2018
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes. Closes #2471.
magnumripper
added a commit
that referenced
this issue
Feb 2, 2018
and ChaCha20 and uses the new fast AES code (which is the heavy part). Closes #2471.
magnumripper
added a commit
that referenced
this issue
Feb 2, 2018
and ChaCha20 and uses the new fast AES code (which is the heavy part). Closes #2471.
magnumripper
added a commit
that referenced
this issue
Feb 2, 2018
and ChaCha20 and uses the new fast AES code (which is the heavy part). Closes #2471.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The KDF of KeePass is pretty unique and the work intensive parts of the KDF involve AES.
The text was updated successfully, but these errors were encountered: