-
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
Keepass OpenCL format. #3131
Keepass OpenCL format. #3131
Conversation
@kholia this is important. We really really need to reject unsupported hashes, always and forever. In this case the [CPU] format would bail out in an awkward way - which is better than nothing - but the correct behavior is rejecting them in |
ef66f84
to
224891b
Compare
Thanks @magnumripper. I missed this opportunity to make |
0f6b470
to
221e274
Compare
I really can't see WTH is wrong with this format. On a few devices, it works like a champ. On others it fails. On some it works fine with LWS=1 (this might be a clue) but not otherwise. I have stared at the code for 24h to no avail. Something must be amiss, but WHAT!? @kholia can you try it out and see if whatever GPU and driver you use work or not, or if it happens to reveal some clue? |
This is interesting. Fails a normal test:
...but passes with LWS=1:
...however when using --test-full instead, it works fine with any LWS:
|
Quick notes,
Update: Disabling Twofish and ChaCha test vectors doesn't seem to improve the situation. I will focus on getting |
It works perfectly fine with nvidia drivers 384.90 and 384.111 (Ubuntu packages) It also works fine with Intel’s CPU driver 1.2.0.42. I think we’re seeing driver bugs. |
29a6ada
to
8cb2636
Compare
and ChaCha. Also fixes a bug in shared valid() - it didn't reject unsupported hashes. Closes #2471.
I tried changing to a whole different AES implementation (not pushed here) but it didn't change a thing with the failing runtimes. |
@kholia I found that the other AES code we have (introduced with WPA CMAC) is 10x faster. It doesn't seem to fix the issues but anyway I will re-work the whole shebang and issue a new PR later. |
All the best for the next attempt @magnumripper! I was hoping to trace the OpenCL kernel to see where things are going wrong but I ran out of debugging energy. |
No description provided.