Skip to content
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

Issue with -dump when only one base64-encoded executable found #9

Closed
R3MRUM opened this issue Jul 10, 2019 · 1 comment
Closed

Issue with -dump when only one base64-encoded executable found #9

R3MRUM opened this issue Jul 10, 2019 · 1 comment

Comments

@R3MRUM
Copy link
Owner

R3MRUM commented Jul 10, 2019

If single base64 executable detected, running -dump results in each individual byte being written to its own file, resulting the the creation of thousands of files.

R3MRUM added a commit that referenced this issue Jul 15, 2019
Fixed Issue #9: #9. -dump switch where only a single encoded executable is present resulted in each byte in the executable being written to individual files.
@R3MRUM
Copy link
Owner Author

R3MRUM commented Jul 15, 2019

Fixed in v4.2

@R3MRUM R3MRUM closed this as completed Jul 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant