How elleoma/facinus works
Project type and purpose
• This is an operations‐oriented deployment tool (“FACINUS”) for Ubuntu/Debian machines. It automates installing and configuring:
• SSH server
• Wake-On-LAN support
• A “fake” power-off script to keep the machine alive
• gsocket tunnel for remote access
• A lightweight Apache+PHP web interface for administration and logs
• Stealth/evasion techniques
• The README and scripts target command-line installers and a simple web UI.
File structure
• Top‐level:
• config/ – default configuration scripts
• install – entrypoint script that orchestrates everything
• scripts/ – modular shell scripts (dependencies, deploy modes, detection, script generation, argument parsing)
• web/ – static + PHP files for the web interface and a log-receiver endpoint
• screenshots/ – reference images of the UI
• Deployment variations under scripts/deploy/ allow full, minimal, quiet, etc.
• web_setup.sh – helper to place web files and configure Apache.
• .gitignore and README.md sit at root.
README
• Confirms purpose and major features.
• Describes URLs for deployment front page, admin panel, log receiver.
• Mentions gsocket service, stealth, power-off, WOL.
Main components and their interactions
a. Components:
1. Administrator’s workstation (browser)
2. Target Ubuntu/Debian server (the machine receiving the install)
3. Installer scripts (shell scripts under root)
4. Apache HTTPD + PHP backend
5. Web frontend (HTML/CSS/JS in web/)
6. gsocket daemon/service
7. SSH daemon
8. WOL module (shell scripts invoking ethtool/magic packets)
9. Logging subsystem (PHP log_receiver.php + file store)
10. “Fake power-off” watchdog
b. Relationships & data flows:
• Admin triggers sudo ./install on the target.
• install → scripts/process_args, detect_system → install dependencies → configure SSH, WOL, stealth.
• web_setup.sh copies web files into Apache’s document root.
• install registers gsocket service and starts it, making the server reachable externally.
• The web interface allows admin to view logs, retrieve secrets, and generate client-side setup commands. Those commands use curl to pull gsocket-based bootstrapping.
• log_receiver.php ingests client-side logs and stores them.
c. Architectural patterns:
• Script-driven orchestration layered on Linux services.
• Simple 3-tier model: Shell/CLI installer → Web backend (PHP) → Frontend UI (HTML/CSS/JS).
• Modular shell scripts for separation of concerns (dependency detection, deployment modes).
d. Key technologies:
• Bash shell scripting, pacman/APT package calls
• Apache2 + PHP
• gsocket.io service
• SSHD, ethtool (for WOL), inotify/timers for fake power-off