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
Using unipacker as a package & Parallel Calls #44
Comments
We can try to draft a PR if you think this is a good idea. |
Thanks for your interest in integrating unipacker! Both suggestions sound like good ideas. The log level customization is probably not that interesting for the interactive shell use case, but I could imagine that the headless mode, which I suppose you are using primarily, would benefit from this. |
Thanks a lot! One more thing when using it as a package: when pe file is open with https://github.com/unipacker/unipacker/blob/master/unipacker/core.py#L394 Error when trying to delete the original file:
One option is to close the PE object directly: erocarrera/pefile#214 f = open(path, "rb")
file_bytes = f.read()
f.close()
pe = pefile.PE(data=file_bytes) Thanks a lot. |
Ah I think pefile mmaps the file instead of reading it completely. Reading it like you did it should make no difference for our use case, as we need to copy the bytes anyway |
I'll take care of the logging part at a later point, probably in a few days. If you need it earlier, feel free to draft a quick PR |
wow thanks a lot for the commits! that's fast! 🚀 we can update the logging part, as well as the conflict of |
Alright, the new release including your newest changes is now out. Expect the CI build to be done in around 40 minutes, and afterwards the package will be pushed to PyPi |
Hello, thanks a lot for the great work! There are two minor things that we would love to adjust for integration purpose. It will be great if we can adjust the verbosity of the printing or logging level with log.info/error. Also If we understand the code correctly, the current implmentation always generate
unpack.exe
and then move the the user supplieddest
path. However, this prevents us having parallel runs for unpacking (they always ends up the same file). Could we make it part of the arguments for UnpackerEngine? So far our workaround is:Again, thanks a lot for the great work!
The text was updated successfully, but these errors were encountered: