{"id":314,"date":"2006-08-23T21:58:40","date_gmt":"2006-08-24T04:58:40","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/mounting-an-executable\/"},"modified":"2006-08-23T22:04:31","modified_gmt":"2006-08-24T05:04:31","slug":"mounting-an-executable","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/mounting-an-executable\/","title":{"rendered":"Mounting An Executable"},"content":{"rendered":"

I was studying the Executable & Linking Format (ELF) recently. I realized how hierarchically it is organized. Nowadays, whenever I think of something hierarchical, for some reason, I think of cramming it into a filesystem structure via FUSE<\/a>. Imagine mounting an executable file as a filesystem. One directory could have a list of exported function names. When reading those files, it would automatically disassemble that section of the file. <\/p>\n


\n\"Executable\"
\n<\/center><\/p>\n

I’m working off of the ‘readelf -a’ command here. There would be a directory at the top level called sections\/ and would contain <\/p>\n

\r\n  .interp\/\r\n  .hash\/\r\n  .dynsym\/\r\n  .dynstr\/\r\n<\/pre>\n
And so on. It might be a little tricky because those names have dots in front of them. Another directory can list shared libraries and have symbolic links to the correct libraries. Another directory will list the exported, public symbols. Opening these files would disassemble the functions for display in whatever text editor you want. Of course, not all of the interesting stuff is found at the public entry points, so it will be necessary to employ heuristics to locate other, private function entry points.<\/p>\n
For bonus points, make the filesystem writable. This will allow annotations in the disassembled source. This will probably require that a “work” copy of the binary to be stored in the user’s home directory.<\/p>\n","protected":false},"excerpt":{"rendered":"
I was studying the Executable & Linking Format (ELF) recently. I realized how hierarchically it is organized. Nowadays, whenever I think of something hierarchical, for some reason, I think of cramming it into a filesystem structure via FUSE. Imagine mounting an executable file as a filesystem. One directory could have a list of exported function […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23],"tags":[],"class_list":["post-314","post","type-post","status-publish","format-standard","hentry","category-outlandish-brainstorms"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t