-
Notifications
You must be signed in to change notification settings - Fork 11
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
MemZipLoader won't load #1
Comments
Same with IDA Pro 7.6.210427:
|
Hi, can you please run IDA with "-z" option and upload the log, I will review it and upload a fix. |
Relevant part (guessing), where
|
Ok, I think I figured it out.
|
Hm indeed these are not the same version, but it still won't load:
IDA logs:
|
Same situation here, even with the provided zip file :( |
Sorry about that I will update you when it's fixed.
Rusetsky Roman
…On Wed, May 19, 2021, 22:10 4rchib4ld ***@***.***> wrote:
Same situation here, even with the provided zip file :(
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACW3YMYV25SDPU7O45WZFGLTOQELDANCNFSM44J2AI7A>
.
|
Don't worry, it really should have been a native feature of IDA Pro in the beginning. Given the amount of time I had my samples deleted by the local AV I don't understand why it's still not the case though, surely we're not the only IDA Pro customers who had troubles when touching the disk. While in theory we should always have a detonation VM handy with no AV to run IDA Pro, erm, reality is a complex thing. |
Hi, and THANK YOU VERY MUCH for that plugin, I also get annoyed by McAfee whenever reversing binaries, and popping a full VM just to unpack generic malware is annoying.
I downloaded the archive and ran the following script:
Integrity check:
When loading IDA Pro, I only see the UrlLoader being loaded, the MemZipLoader isn't loaded:
I am using IDA Pro 7.5.201028.
I'm willing to provide assistance to diagnose this on request, thanks again.
The text was updated successfully, but these errors were encountered: