2 ms·
It's turned into one of my favorite topics too. It's weird how all the tools out there are all about the ELF sections. Apparently the sections are where all th
by matheusmoreira 3y ago
It's turned into one of my favorite topics too.
It's weird how all the tools out there are all about the ELF sections. Apparently the sections are where all the fun stuff gets stored and the program headers are just some kernel wizardry nobody really cares about.
The section/segment dichotomy exists so that kernels need not load needless stuff onto memory. In practice it means things like ELF symbol tables are not available for introspection by the program. If pointers to those symbols are required, the easiest way is to get the ELF interpreter to give them to the program. If it's a static executable then there's no interpreter and things get annoying fast. Most solutions I've seen involve reading the program's own executable into memory and parsing the ELF structures, essentially duplicating the work of the kernel's ELF loader. Alternatively, one may engage in this incredibly fun activity called linker scripting.
I chose to hack together an ELF patching tool in order to get Linux to automatically load arbitrary ELF file segments onto memory. Along the way I requested some linker features and actually got them!
https://github.com/lone-lang/lone/blob/master/source/tools/lone-embed.c https://github.com/lone-lang/lone/blob/master/source/tools/l...
With these tools I made it possible for my language's interpreter to load programs embedded inside itself.
https://www.matheusmoreira.com/articles/self-contained-lone-lisp-applications https://www.matheusmoreira.com/articles/self-contained-lone-...
I really want to see this feature get adopted by the mainstream languages. Apparently no one else ever thought of it.
- nneonneo 3y agoPython one-file-packagers such as PyInstaller typically use the technique of shoving the entire Python standard library into the executable as a zip file; Python can natively import scripts straight out of .zip files (zipimport) so you just point `sys.path` at the executable and voila, self-contained Python in a single binary. (Note that this doesn't immediately solve the problem of using native code dynamic libraries, which usually have to get unpacked anyway or use hacky custom loaders). One year, for DEF CON CTF, we had to write all of our exploits as single ELF binaries targeting a minimal OS (DARPA CGC) with only seven system calls (exit, read, write, select, malloc, free, getrandom). Since writing exploits in C sucks, I packaged Python for the OS instead, creating a "virtual filesystem" for including Python code (including standard library) as a static chunk of data and implementing open/read/write on top of the VFS. This was really quite successful for us, as we were able to write very high-level Python code for a full, functioning Python interpreter in our exploits.
- ithkuil 3y agoNice. But the beauty of GP's approach is that you don't need to issue another open syscall to open argv[0] in order to access (read or mmap) your code but instead just piggy back on what the kernel just did for your entry point anyway. Except for the beauty of the approach, I'm not sure what the practical advantages are. Are there cases where a process wouldn't have permissions to access its own executable or argv[0] value is unreliable? Can you exec on a file descriptor of a deleted file? EDIT: or would /proc/self/exe always point to something the process could open?
- loeg 3y agoThe benefit of GP's approach is mostly just elegance. You can reliably introspect the (mapped) program headers with getauxval AT_PHDR.
- nneonneo 3y agoI believe the process always holds the binary open as a "txt" file descriptor (check lsof), so opening `/proc/self/exe` always works. You can even execve a "memfd", an in-memory "file" which is not in the filesystem (distinct from a ramdisk file, which is a file sitting on an in-memory filesystem). /proc/self/exe still works even in that case, even when the original memfd is closed. Note that argv[0] can never be relied on 100%. The vast majority of programs will set it correctly (especially since many programs will malfunction if provided bogus argv[0]), but a caller has full control over argv[0] and can set it to anything, including a NULL pointer (by simply passing an empty argv array).
- ithkuil 3y agoThere is the possibility /proc is not mounted, right?
- matheusmoreira 3y agoAbsolutely. It's certainly not mounted automatically after Linux boots and depending on the system's configuration it might never get mounted at all. Maybe it could even use some other path. One of my long term goals with the programming language I posted is to boot Linux directly into the interpreter and bring up the entire system from inside it. Not only will /proc not be mounted, my program's gonna be the one that mounts it. So I decided to avoid using tricks like reading /proc/self/exe.
- loeg 3y ago> this incredibly fun activity called linker scripting Indeed. :-) > I chose to hack together an ELF patching tool in order to get Linux to automatically load arbitrary ELF file segments onto memory. Interesting. It's clever. I think a slightly more conventional design would be to have just a LOAD segment for your embedded module (for the loader) with some self-describing application-specific header describing the length of the embedded script (for your interpreter), rather than using the ELF Segments table (LOOS+0xc6f6e65) for that. A dumber hack with less cool learning about ELF might be to just have a magic number variable in your interpreter that is initialized bogus and then patched to point at an offset by the patching tool.