[GH-ISSUE #44] Add firmware, embedded-system, and filesystem-image analysis #33

Closed
opened 2026-10-15 18:20:14 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @morluto on GitHub (Jul 12, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/44

Goal

Support offline investigation of firmware and embedded-system artifacts as graphs of containers, filesystems, executables, configuration, and hardware-facing behavior.

Scope

  • raw firmware images, update packages, bootloaders, kernels, and filesystem images
  • ELF binaries across common embedded architectures
  • UEFI and device firmware metadata
  • SquashFS, cramfs, ext, FAT, CPIO, and vendor container discovery
  • entropy, compression, encryption, signatures, checksums, and partition maps
  • configuration, certificates, endpoints, init systems, services, and update logic
  • optional integrations with binwalk, Ghidra, Rizin, QEMU, and architecture toolchains

Safety

  • Default to offline, read-only extraction and static inspection.
  • Contain recursive extraction and enforce depth, size, and file-count budgets.
  • Treat emulation, hardware access, flashing, and network interaction as separate approval-gated capabilities.
  • Preserve parent-child hashes and exact extraction provenance.

Acceptance criteria

  • Representative firmware fixtures yield deterministic nested artifact graphs.
  • Architecture, filesystems, executables, services, and high-value configuration are discoverable.
  • Recursive extraction cannot escape its output root or exhaust unbounded resources.
  • Unsupported formats and encrypted regions remain explicit residual unknowns.
Originally created by @morluto on GitHub (Jul 12, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/44 ## Goal Support offline investigation of firmware and embedded-system artifacts as graphs of containers, filesystems, executables, configuration, and hardware-facing behavior. ## Scope - raw firmware images, update packages, bootloaders, kernels, and filesystem images - ELF binaries across common embedded architectures - UEFI and device firmware metadata - SquashFS, cramfs, ext, FAT, CPIO, and vendor container discovery - entropy, compression, encryption, signatures, checksums, and partition maps - configuration, certificates, endpoints, init systems, services, and update logic - optional integrations with binwalk, Ghidra, Rizin, QEMU, and architecture toolchains ## Safety - Default to offline, read-only extraction and static inspection. - Contain recursive extraction and enforce depth, size, and file-count budgets. - Treat emulation, hardware access, flashing, and network interaction as separate approval-gated capabilities. - Preserve parent-child hashes and exact extraction provenance. ## Acceptance criteria - Representative firmware fixtures yield deterministic nested artifact graphs. - Architecture, filesystems, executables, services, and high-value configuration are discoverable. - Recursive extraction cannot escape its output root or exhaust unbounded resources. - Unsupported formats and encrypted regions remain explicit residual unknowns.
Author
Owner

@morluto commented on GitHub (Jul 20, 2026):

Split into focused child issues:

These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.

<!-- gh-comment-id:5023445129 --> @morluto commented on GitHub (Jul 20, 2026): Split into focused child issues: - [ ] #370 These replace the broad remaining scope in this issue. Closing this parent can happen once all children are closed.
Author
Owner

@morluto commented on GitHub (Jul 20, 2026):

Closing as out of scope / premature for the current local CLI/MCP reverse-engineering focus: no supporting code exists, and these areas should be revisited only after in-tree providers and the public boundary are stable.

<!-- gh-comment-id:5023568087 --> @morluto commented on GitHub (Jul 20, 2026): Closing as out of scope / premature for the current local CLI/MCP reverse-engineering focus: no supporting code exists, and these areas should be revisited only after in-tree providers and the public boundary are stable.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#33
No description provided.