Skip to content

Add REA reverse-engineering LXC helper - #2695

Open
Estcool9 wants to merge 3 commits into
community-scripts:mainfrom
Estcool9:feat/rea-reverse-engineering-mcp
Open

Estcool9 wants to merge 3 commits into
community-scripts:mainfrom
Estcool9:feat/rea-reverse-engineering-mcp

Conversation

@Estcool9

@Estcool9 Estcool9 commented Nov 21, 2026 •

Copy link
Copy Markdown

✍️ Description

Adds a Debian 13 unprivileged LXC helper for REA, an MCP-based reverse-engineering toolkit. The installer provisions Node.js 24, Temurin JDK 25, Ghidra, and a checksum-verified JADX MCP adapter, then runs REA under a dedicated unprivileged systemd account; release updates use the DevScripts helpers while the REA CLI itself is updated through npm. REA's HTTP MCP endpoint does not provide its own client authentication, so the metadata warns operators to restrict TCP 8765 to a trusted gateway and terminate OAuth 2.0 at a TLS-enabled MCPHub; the upstream project logo is used because no matching selfhst icon is published. The equivalent manual deployment has been tested on Proxmox VE 9.2.32, including healthy Ghidra/JADX diagnostics and MCPHub discovery of 263 tools and 6 prompts; the exact DevScripts build_container flow still needs end-to-end testing. GPT-6 was used to draft and revise the scripts; the output was reviewed against the repository guidance and statically checked (reasoning-effort metadata is unavailable in this session).

🔗 Related PR / Issue

Link: #2696

✅ Prerequisites

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – The submitted DevScripts build_container path has not yet completed an end-to-end test.
  • No breaking changes – This adds a new script only.
  • No security risks – REA's HTTP listener has no built-in authentication; operators must restrict access to a trusted MCP gateway/firewall.

🧩 Script

Name: REA

Tool: REA is a reverse-engineering CLI and MCP server for static analysis of binaries, applications, and firmware. It integrates Ghidra and JADX and exposes analysis workflows to AI agents and developer tools.

🗂️ Category

  • CT – LXC container (ct/ + install/)
  • VM – Virtual machine (vm/)
  • Addon – tools/addon/
  • PVE Tool – tools/pve/
  • Other

🖥️ Platform – tested on

  • Proxmox VE – CT 107 was created on PVE 9.2.32 and the manually deployed app and both providers work. The submitted Helper script itself remains to be tested end to end.
  • Incus

🏗️ Architecture

  • arm64 supported
  • arm64 not tested
  • arm64 not supported – The Ghidra distribution used here includes Linux x86_64 native components; this helper is intentionally amd64-only.

🛠️ Type of Change

  • 🐞 Bug fix
  • ✨ New feature
  • 💥 Breaking change
  • 🆕 New script
  • 🌍 Website update
  • 🔧 Refactoring / Code Cleanup
  • 📝 Documentation update

🔍 Code & Security Review

  • Follows AGENTS.md & script-creator guidance
  • Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
  • No hardcoded credentials
  • No Docker / Docker Compose – REA is installed bare-metal.
  • No git pull – Releases use DevScripts release helpers and npm.

📋 Additional Information

Static checks passed:

  • bash -n ct/rea.sh install/rea-install.sh
  • ShellCheck 0.10.0 (excluding SC1090 for the standard dynamic core loader)
  • python3 -m json.tool json/rea.json
  • git diff --check

The test thread is #2696. REA's endpoint has no native authentication; the generated container therefore must not expose TCP 8765 to untrusted networks. Configure a trusted gateway and host firewall before allowing remote clients.


📦 Application Requirements (for new scripts)

  • The application is at least 6 months old – GitHub repository created 2026-04-14.
  • The application is actively maintained – Latest upstream push 2026-11-21.
  • The application has 1,000+ GitHub stars – GitHub API reported 472,649 at submission time.
  • Official release tarballs are published – GitHub Releases provide source archives; the CLI is also published on npm.
  • I understand that not all scripts will be accepted due to various reasons and criteria by the community-scripts ORG.

🌐 Source


🤖 AI Assistance

  • No AI used
  • AI was used – The scripts were built using AGENTS.md and .github/agents/pve-script-creator.agent.md as guidance and reviewed against those rules.

LLM usage: GPT-6 drafted and revised the helper scripts, metadata and this PR description. The scripts were statically checked; the full DevScripts build_container test remains pending. Reasoning/thinking effort is not exposed in this session metadata.

@github-actions

github-actions Bot commented Nov 21, 2026 •

Copy link
Copy Markdown
Contributor

✅ Requirements check passed. Thanks for fixing the description — the stale mark has been removed.

@github-actions

Copy link
Copy Markdown
Contributor

Try this branch

The engine and the scripts resolve independently, so this runs the changed
ct/ and install/ scripts against the production engine:

export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/Estcool9/DevScripts-voicestudio/feat/rea-reverse-engineering-mcp
bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/rea.sh")"

Both lines are needed. Without COMMUNITY_SCRIPTS_URL the engine falls back to
main, so curling the branch URL on its own gives you the ct/ script from
this PR and the install/ script from main. Frequently the one you meant to test.

The same command works on an Incus host: the engine detects the platform and
loads the matching backend, while the scripts still come from this branch.

Useful while testing

dev_mode=net logs every fetch with status and URL, which is the quickest way
to confirm the branch is really being used. dev_mode=keep stops a failed
build from deleting the container along with the evidence.

export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/Estcool9/DevScripts-voicestudio/feat/rea-reverse-engineering-mcp
dev_mode=net,keep bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/rea.sh")"
Against a core branch as well

Add COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/OWNER/core/BRANCH
to test an engine change at the same time. The two resolve independently.

@github-actions github-actions Bot added requirements missing PR description misses template items; closes after 7 days unless fixed or keep-open stale new script labels Nov 21, 2026
@github-actions github-actions Bot removed requirements missing PR description misses template items; closes after 7 days unless fixed or keep-open stale labels Nov 21, 2026

Copy link
Copy Markdown
Author

The contributor-side static checks now pass on the latest branch commit (bash -n, ShellCheck 0.10.0, JSON validation and git diff --check). The three PR-triggered Actions runs currently report action_required, and GitHub returns no jobs for them, so there are no failing job logs to fix or rerun yet. Because this PR comes from a public fork, a maintainer with write access needs to approve the workflow runs in the PR UI before CI can execute. The existing manual PVE deployment is working; the end-to-end build_container test remains tracked in #2696.

@Estcool9
Estcool9 marked this pull request as ready for review November 21, 2026 23:20
@Estcool9
Estcool9 requested a review from a team as a code owner November 21, 2026 23:20
@github-actions

Copy link
Copy Markdown
Contributor

Proxmox script test

⏳ Building 2 at ec8f6ab — watch it live (open the test job)

  • ct/rea.sh (pve)
  • ct/rea.sh (incus)

Not built:

  • ct/rea.sh on ARM64: the script sets var_arm64=no

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant