Say I want to combine two binaries into a single one. Is there good prior art for this?
E.g. an entry binary, which does some stuff and then opens the other binary.
Should def be possible, but it's more a question of finding the least hacky version of doing so 
But like seriously. Best I'm seeing is copying files to disk, and executing them. Big downside of this is that it leaves a bunch of artifacts, and takes time. Ideally we could just JMP into where the next file starts or smth, hah.
-
-
Okay, bit anticlimactic but the most reasonable approach seems to be to store the embedded binary as base64 string inside the wrapper program. Then extract to /tmp to set permissions and run it. Simple, and should work!
Show this thread -
This then becomes an exercise in combining files right — because you probably want a tool that can generate these combined files for you. But that seems like a solvable problem! :D
Show this thread -
I'll most likely be able to knock out a demo in less than a day. Might do a fun side track on stream about this, if I can get the prerequisites working first. (E.g. working libcgroup locally; unshare and chroot are ok too
).Show this thread
End of conversation
New conversation -
-
-
If you’re talking Linux or similar: It depends. Do you control the contents of any of the two binaries? If the “child” is a dynamically linked binary (default), the biggest trouble you’d be running into is how the dynamic linker works, which would be hard to emulate…
-
Yeah, it'd be to wrap a binary I created and do stuff like cgroups & unshare with it :D
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.