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.

Sign up for GitHub

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

Jump to bottom

Figure out the best way to handle binaries for modules #57

Closed
byt3bl33d3r opened this issue Mar 27, 2019 · 1 comment
Closed

Figure out the best way to handle binaries for modules #57

byt3bl33d3r opened this issue Mar 27, 2019 · 1 comment
Labels
help wanted Extra attention is needed

Comments

@byt3bl33d3r
Copy link
Owner

This came up in #54, keeping the binaries updated for every module is a hassle and too much work. @maaaaz mentioned that an alias command for the execute-assembly module might do the trick and i think this is probably the best solution. If anyone has a better idea i'm all ears.
@byt3bl33d3r byt3bl33d3r added the help wanted Extra attention is needed label Mar 27, 2019
@byt3bl33d3r
Copy link
Owner Author

Closing since I think i figured out the most sensible way in doing this, all binaries are stored under teamserver/data and get loaded and compressed at runtime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@byt3bl33d3r