Repository navigation
2.0.0
Luma now decodes memory with patterns, boots virtual machines to instrument their kernels, and gains moldable scripting in the spirit of Glamorous Toolkit, with graphics, GPU shaders, sound and the filesystem a snippet away.
Important
Breaking changes
- Labs: the collaboration protocol is now version 2. Clients older than 2.0 cannot join labs.
- Projects: the format changed (schema version 4), so projects saved by older versions will not open. To bring a lab forward, open its link in 2.0 and save.
- Hook packs are gone. A linked instrument folder replaces them.
Patterns
Describe a structure in ImHex's pattern language and lay it over live memory.
- Decode as works on any bytes:
pxdumps,readByteArray()results, bytes in events, and dumps pinned to the notebook. - A field selects its bytes, a byte selects its field, pointers can be followed, and ImHex's visualizers are drawn.
- Patterns get an editor with completions and diagnostics. They live in the project, install from npm, and import from a TypeScript instrument.
- Type over bytes or edit a field in the tree to write live memory, code included.
Virtual machines
Boot a guest from the target picker and attach to its kernel.
- Windows 95 through Me, and XP through 11, boot from your own disk image; Linux boots Alpine without picking a file, on x86, x86-64, arm or arm64.
- On a Mac, macOS guests boot too. Android Studio AVDs boot on any host.
- QEMU comes with Luma on Windows and macOS, and in the Flatpak, Snap and AppImage; the .deb and .rpm use your distribution's.
- The kernel leads the machine's process list. You can attach to processes as well.
- Mark a machine ready and the next boot resumes from that snapshot.
- Choose how QEMU accelerates the guest (emulation, KVM, Hypervisor.framework or Windows Hypervisor Platform), run a QEMU of your own, add arguments, and preview the full command line before booting.
Moldable scripting
A playground and inspector modeled on Glamorous Toolkit's: ask a question in a snippet, then shape how the answer is shown.
- Evaluate in the playground or in a notebook cell. The answer opens in an inspector, and each object you pick opens in the next pane beside it.
- An object says how it wants to be seen. Give your own classes views with
<gtView>: lists, tables, charts, graphs, or a scene you draw yourself. - Graphics, sound and files are a message away: a canvas driven by your own GLSL shaders on the GPU, an eight-channel synthesizer, and the filesystem.
- Your Frida sessions are objects too. Walk their modules, threads and memory, hook a function with a block, decode a pattern at a pointer, or ask radare2.
- Classes and methods you write are kept with the project. What a cell starts stops when it runs again.
It runs on an embedded Pharo image, on Windows, macOS, Linux and iOS.
A native editor
Monaco and its webview are gone. Code is edited in a native text view backed by the Frida compiler's own language server, so completions, hovers and diagnostics agree with the build.
Instruments in folders
Link a folder as a custom instrument: sources beside a package.json.
- Edits in Luma are written through to the folder. Edits on disk are offered as a reload; if both changed, you choose.
- Each instrument has its own npm dependencies, and
luma.rootlets several share code. luma.d.tsis written beside the sources for external editors.
Collaboration
- A project's patterns travel with its lab, and any member can place them.
- The lab's web page shows what a pinned dump decodes to, and notebook cells with their results.
- A change the lab turns away is now reported.
Also
- Files: browse the target's filesystem, drag files in and out, delete.
- Modules: browse a module's contents in the sidebar, Swift types included.
- Gadget: on jailed iOS and Android devices, Luma fetches Frida Gadget and loads it into debuggable apps.
- Agents: MCP tools for patterns, virtual machines, the playground and instrument folders.
- Copy the event stream as text.
- The target picker shows how connecting to a device is going.
- AppImage builds.
- Frida 17.27.4.
Fixes
- Custom instruments failing to compile with TS2304 at injection (#34), also with aliased packages and in tracer hooks.
- Function traces that stopped a few blocks in.
- Disassembly coming back empty for memory outside any module.
- 64-bit integers arriving as empty objects.
- Symbol search in very large modules, such as a kernel, taking many seconds to show a first row.
- Targets without a main module losing their platform and architecture.
- A thread's registers failing to load for x86-64 Linux targets.
- Insights at addresses above
0x7fffffffffffffffcrashing the app. - Labs: a Linux client's messages being dropped by peers; updating a notebook entry wiping its bytes for other members; rereading memory inside an event disconnecting the client; every change being replayed on each join.
- GTK: dialogs whose Save did nothing; the editor not showing a file's reloaded content; links and badges drawn black on current libadwaita.
- The event stream growing the window, and arriving events closing an open context menu.