SSH Fleet Doctor

Overview

Operational visibility through a small, inspectable toolkit.

The project began as SSH-Infiltrator and is evolving into SSH Fleet Doctor. It joins a Bash-based control workflow with a Python command-line monitor for remote resource checks and administrative tasks.

Its public documentation describes health monitoring, logging, backups, reporting, multi-server work, and error handling.

Capabilities

Connect, inspect, record, and respond.

• Connect to authorized SSH hosts
• Inspect CPU, memory, disk, and network statistics
• Execute selected or custom administrative commands
• Record actions for auditing and troubleshooting
• Support scheduled tasks, file backup, and system reports

Architecture

Shell orchestration with a Paramiko-based Python path.

SETUP.sh checks for Python and pip, creates a virtual environment, and installs Paramiko. SSH_Infiltrator.sh provides the interactive shell workflow, while python/SSH_Intruder.py validates host input, creates an SSH client, prompts for credentials when needed, and exposes monitoring and command functions.

Local log files record operational actions for troubleshooting and audit review. Sensitive credentials should never be written into those files.

Validation

Preflight checks before any authorized operational trial.

• Run bash -n against SETUP.sh and SSH_Infiltrator.sh
• Compile-check python/SSH_Intruder.py without connecting to a host
• Confirm Paramiko imports successfully in the virtual environment
• Use a disposable SSH host for read-only CPU, memory, disk, and network monitoring
• Exercise timeout, refused connection, invalid credential, and lost-session paths
• Confirm logs contain useful operational context without secrets

Setup

Start with a disposable or explicitly authorized SSH test host.

• Clone the repository and inspect the scripts before running them
• Run SETUP.sh to create the venv and install Paramiko
• Use a restricted remote user
• Omit password arguments so credentials are prompted instead of exposed in shell history
• Begin with read-only monitoring
• Prefer SSH keys, host-key verification, tested backups, and least privilege for non-disposable systems

Safety

Administrative power requires explicit boundaries.

The tool can invoke disruptive remote operations. It should only be used on systems you own or are explicitly authorized to administer, beginning with a disposable test host.

Never point the toolkit at an unknown or production host until every enabled action has been reviewed.

Publication note

Static, crawlable case study.

This page contains the substantive project description directly in HTML. The existing GLab project catalogue and JavaScript interface can continue to operate independently.