[PR #6124] fix(ghidra): point Windows ELF rejection to WSL2 fallback #7148

New issue

Open

opened 2026-11-01 21:45:44 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-11-01 21:45:44 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6124
Author: @Tapraj-Pathak
Created: 10/21/2026
Status: 🔄 Open

Base: main ← Head: fix/windows-ghidra-elf-wsl2-fallback

📝 Commits (4)

915d811 fix(ghidra): point Windows ELF rejection to WSL2 fallback
88ade0f Update src/ghidra/GhidraProvider.ts
3262f6e Merge branch 'main' into fix/windows-ghidra-elf-wsl2-fallback
529d1f9 Merge branch 'main' into fix/windows-ghidra-elf-wsl2-fallback

📊 Changes

4 files changed (+41 additions, -3 deletions)

View changed files

📝 .agents/skills/reverse-engineer-anything/references/connection-and-recovery.md (+4 -2)
📝 docs/windows-ghidra-p0.md (+35 -0)
📝 src/ghidra/GhidraProvider.behavior.test.ts (+1 -0)
📝 src/ghidra/GhidraProvider.ts (+1 -1)

📄 Description

Problem

Windows Ghidra P0 intentionally admits PE and raw 6502 targets only, but ELF targets such as Android ARM64 libapp.so previously failed without a direct remediation path. Re-running doctor or setup could not resolve this format boundary, so users were left with a supported target rejection and no recovery guidance.

Change

Document the Windows P0 ELF gap and the supported-target boundary.
Add a WSL2 Linux Ghidra fallback for Windows ELF analysis.
Point target_format_unsupported at the WSL2 fallback section.
Update the bundled recovery table so agents stop retrying setup when every provider rejects the target format.

This does not widen Windows P0 admission or change its native security boundary.

Validation

Local validation performed:

npm.cmd run test:focused -- src/ghidra/GhidraProvider.behavior.test.ts
npm.cmd run docs:check
npx.cmd oxfmt --check ...
git diff --check

The focused Ghidra validation and docs check completed successfully locally. However, the repo-level required CI gate still reports failures in:

static
windows-native-build
package-e2e

Those failures are tracked at the CI lane level and are not a passing signal for this PR.

Author readiness

Human owner: @Tapraj-Pathak

I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
I declare this PR ready for maintainers to review after the required CI lanes are green.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/6124 **Author:** [@Tapraj-Pathak](https://github.com/Tapraj-Pathak) **Created:** 10/21/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/windows-ghidra-elf-wsl2-fallback` --- ### 📝 Commits (4) - [`915d811`](https://github.com/morluto/rea/commit/915d811f54bfe53cb479004c6a629760c85c49ce) fix(ghidra): point Windows ELF rejection to WSL2 fallback - [`88ade0f`](https://github.com/morluto/rea/commit/88ade0fe6a32c8c1fd01383ea308cf94ff773fec) Update src/ghidra/GhidraProvider.ts - [`3262f6e`](https://github.com/morluto/rea/commit/3262f6ea2d95fe88e46b1fbc5a4a6efb37260114) Merge branch 'main' into fix/windows-ghidra-elf-wsl2-fallback - [`529d1f9`](https://github.com/morluto/rea/commit/529d1f9bf8bd4ed54188ce81c29a1cfea30280a3) Merge branch 'main' into fix/windows-ghidra-elf-wsl2-fallback ### 📊 Changes **4 files changed** (+41 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `.agents/skills/reverse-engineer-anything/references/connection-and-recovery.md` (+4 -2) 📝 `docs/windows-ghidra-p0.md` (+35 -0) 📝 `src/ghidra/GhidraProvider.behavior.test.ts` (+1 -0) 📝 `src/ghidra/GhidraProvider.ts` (+1 -1) </details> ### 📄 Description ## Problem Windows Ghidra P0 intentionally admits PE and raw 6502 targets only, but ELF targets such as Android ARM64 `libapp.so` previously failed without a direct remediation path. Re-running `doctor` or `setup` could not resolve this format boundary, so users were left with a supported target rejection and no recovery guidance. ## Change - Document the Windows P0 ELF gap and the supported-target boundary. - Add a WSL2 Linux Ghidra fallback for Windows ELF analysis. - Point `target_format_unsupported` at the WSL2 fallback section. - Update the bundled recovery table so agents stop retrying setup when every provider rejects the target format. This does not widen Windows P0 admission or change its native security boundary. ## Validation Local validation performed: - `npm.cmd run test:focused -- src/ghidra/GhidraProvider.behavior.test.ts` - `npm.cmd run docs:check` - `npx.cmd oxfmt --check ...` - `git diff --check` The focused Ghidra validation and docs check completed successfully locally. However, the repo-level required CI gate still reports failures in: - `static` - `windows-native-build` - `package-e2e` Those failures are tracked at the CI lane level and are not a passing signal for this PR. ## Author readiness Human owner: @Tapraj-Pathak - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for maintainers to review after the required CI lanes are green. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-11-01 21:45:44 +00:00

bsakaguchi referenced this issue

2026-11-03 13:39:33 +00:00

[PR #7148] [CLOSED] test(skill): guard bundled SKILL.md references against the advertised MCP catalog #7675