-
Notifications
You must be signed in to change notification settings - Fork 0
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
something fishy here in px1kcr-clarify.py #1
Comments
it might be related to this bug: angr/claripy#241 (comment) |
But if we only remove "IPython.embed()", and replace ONLY the ct with the test ct, it also does not finish. |
it would be interesting to see how all those asserts work with a solver that has not seen any asserts before. so making a copy of the solver before the |
or alternatively use asserts with known good testvectors, do the final solve with an unrelated target vector. |
i'll try that. i'm afraid you are right that somehow the "the expected solution is built into the attack" by leaking through the asserts. |
I will stay tuned. |
hmm, it seems that if i solve for a different ciphertext (using a different key as well) while having the asserts for the original ciphertext/key in there the code in line 318: sol = s.eval(key, 1, extra_constraints=[ciphertext == ct_test]) indeed times out, and thus it seems invalidates my attack. what is strange though, is that (this was a few years ago) i seem to remember actually testing the attack by first building the model (which takes ~50 sec) and then feeding it different ciphertexts and it solved them each in about 4 sec while reusing the model. maybe my memory plays games with me, but until i can recover exactly how and why that worked back then, i guess i have to say that the attack is broken. :/ |
however painful the (hopefully temporary) result, thank you for your feedback and your interest in all this, it is much appreciated. |
I am truly bummed. I was hoping to learn from this in anticipation of an upcoming challenge on MysteryTwister. If you can find any old files from this attack, I have about three weeks that I can use to help figure it out. |
If I remove these lines:
then the program never finishes. It appears that the expected solution is built into the attack.
The text was updated successfully, but these errors were encountered: