Skip to content

Add REA reverse-engineering LXC helper - #2695

Draft
Estcool9 wants to merge 1 commit into
community-scripts:mainfrom
Estcool9:feat/rea-reverse-engineering-mcp
Draft

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

Conversation

@Estcool9

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, a checksum-verified JADX MCP adapter, and a dedicated unprivileged systemd service with Ghidra/JADX health checks. REA's HTTP MCP listener has no built-in OAuth, so the catalog metadata explicitly requires restricting TCP 8765 to a trusted MCP gateway and terminating OAuth 2.0 at a TLS-enabled MCPHub. The current stack was deployed and provider-checked manually in CT 107 on Proxmox VE; the new helper's complete DevScripts build_container flow has not yet been exercised, so this PR is submitted as a draft for end-to-end testing.

🔗 Related PR / Issue

Link: #

✅ Prerequisites

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No breaking changes – Existing functionality remains intact.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🧩 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 and the manually deployed REA service and both providers work. The submitted helper flow itself remains untested end to end.
  • Incus

🏗️ Architecture

  • arm64 supported
  • arm64 not tested
  • arm64 not supported – This initial helper intentionally enables amd64 only; ARM64 is not claimed as supported.

🛠️ Type of Change

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

🔍 Code & Security Review

  • Follows CODE-AUDIT.md & CONTRIBUTING.md guidelines
  • Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
  • No hardcoded credentials
  • No Docker / Docker Compose – The application is installed bare-metal; Docker is not used.
  • No git pull – Updates use the official release helpers and npm.

📋 Additional Information

Static checks performed on the three new files:

  • bash -n ct/rea.sh install/rea-install.sh
  • ShellCheck 0.10.0 with SC1090 excluded for the standard dynamic DevScripts helper loader
  • python3 -m json.tool json/rea.json
  • git diff --check

The live manual deployment has healthy Ghidra and JADX provider diagnostics, and REA is reachable through a private MCPHub route. It is not a substitute for exercising this PR through the DevScripts container builder. The MCP endpoint is intentionally unauthenticated at the application layer; keep it private behind a trusted gateway/firewall.


📦 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 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 publish source archives; the REA CLI is also distributed 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 – I confirm the scripts were built using AGENTS.md and .github/agents/pve-script-creator.agent.md as guidance, and the output has been reviewed and corrected to match those guidelines.

LLM usage: GPT-6 (reasoning level not exposed in the session metadata) was used to draft and revise the helper scripts, metadata, and this PR description. The resulting files were checked against the repository guidance, shell syntax, ShellCheck, JSON validity, and the upstream update-helper conventions. The full DevScripts build_container test is still pending.

@github-actions

Copy link
Copy Markdown
Contributor

⚠️ Not ready for review yet

@Estcool9, this pull request is missing the following:

  • One arm64 support option (arm64 supported, arm64 not tested, or arm64 not supported) must be checked

Edit the PR description to fix it — no new PR needed. This check runs again on every edit and clears itself once everything is in place.

Until then the PR is marked stale and will be closed in 7 days.


@community-scripts/contributor please take a look: close it, comment, or set keep-open to keep it.

@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

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

Labels

new script requirements missing PR description misses template items; closes after 7 days unless fixed or keep-open stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant