Stefan Marsiske
Stefan Marsiske
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.
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...
however painful the (hopefully temporary) result, thank you for your feedback and your interest in all this, it is much appreciated.
sorry for the late answer, another project took all my attention. what do you mean with hard-coding the path in line 33? what would be that path? i have no...
googled a bit, it seems that brew doesn't install libraries in any of /usr/lib lor /usr/local/lib but somewhat random locations instead. i don't really know how to guess these correctly,...
oh, so you say i get the path using `os.system('pkg-config --libs')` instead of `find_library`, hmm, that could work, not nice, but it sounds workable..
not sure we are talking about the same thing. this is about python ctypes.find_library not finding libsodium, has nothing to do with cmake.
hmm, `pkg-config -l` doesn't work it only gives me the linker flags, like `-lsodium` not a path.