Custom Builds
Create custom Haxinator 2000 firmware images tailored to your specific needs and use cases.
Overview
The Haxinator 2000 build system allows you to create custom firmware images with:
- Custom Tools: Add your own networking and security tools
- Pre-configured Settings: Bake in your preferred configurations
- Reduced Size: Remove unused components for smaller images
- Specialized Builds: Create purpose-built images for specific scenarios
Build Environment Setup
Prerequisites
Set up your build environment:
# Install required packages (Ubuntu/Debian)
sudo apt update
sudo apt install git build-essential python3 python3-pip
# Clone the Haxinator 2000 repository
git clone https://github.com/MoreHax/haxinator2000.git
cd haxinator2000
Build Dependencies
Install build dependencies:
# Install Python dependencies
pip3 install -r requirements.txt
# Install additional build tools
sudo apt install qemu-user-static debootstrap
Build Configuration
Base Configuration
The build system uses configuration files to customize builds:
# config/custom-build.yml
build:
name: "Custom Haxinator"
version: "2.0-custom"
base_image: "raspios-lite"
features:
dns_tunneling: true
icmp_tunneling: true
ssh_tunneling: true
openvpn: true
custom_tools: true
custom_packages:
- nmap
- tcpdump
- wireshark-common
- aircrack-ng
Tool Selection
Choose which tools to include:
Network Analysis Tools
- nmap: Network discovery and security auditing
- tcpdump: Packet capture and analysis
- wireshark: Network protocol analyzer
- netcat: Network utility for debugging
Tunneling Tools
- stunnel: SSL tunneling proxy
- proxychains: Proxy chains for anonymity
- tor: The Onion Router for anonymity
- shadowsocks: Secure proxy protocol
Security Tools
- aircrack-ng: WiFi security auditing
- hashcat: Password recovery tool
- john: Password cracking tool
- metasploit: Penetration testing framework
Custom Tool Integration
Adding Custom Scripts
Include your own scripts and tools:
# Create custom tools directory
mkdir -p custom/tools
# Add your custom scripts
cp my-custom-tool.py custom/tools/
cp my-config-script.sh custom/tools/
Web Interface Customization
Customize the web interface:
// custom/web/js/custom.js
// Add custom JavaScript functionality
// custom/web/css/custom.css
/* Add custom styling */
// custom/web/templates/custom.html
<!-- Add custom pages -->
Service Integration
Add custom services:
# custom/services/my-service.service
[Unit]
Description=My Custom Service
After=network.target
[Service]
Type=simple
ExecStart=/usr/local/bin/my-service
Restart=always
[Install]
WantedBy=multi-user.target
Build Process
Standard Build
Build a standard custom image:
# Configure build
cp config/custom-build.yml config/build.yml
# Start build process
./build.sh --config config/build.yml
# Build output
ls output/haxinator-custom-*.img
Advanced Build Options
Use advanced build options:
# Minimal build (smaller image)
./build.sh --minimal --config config/minimal.yml
# Debug build (with debugging tools)
./build.sh --debug --config config/debug.yml
# Headless build (no GUI tools)
./build.sh --headless --config config/headless.yml
Specialized Builds
Penetration Testing Build
Create a pentest-focused build:
# config/pentest-build.yml
features:
penetration_testing: true
custom_packages:
- metasploit-framework
- nmap
- aircrack-ng
- hashcat
- john
- sqlmap
- nikto
- dirb
Stealth Build
Create a maximum stealth build:
# config/stealth-build.yml
features:
icmp_tunneling: true
dns_tunneling: true
stealth_mode: true
optimizations:
minimal_footprint: true
encrypted_storage: true
secure_boot: true
Corporate Build
Create a corporate-friendly build:
# config/corporate-build.yml
features:
enterprise_wifi: true
certificate_management: true
compliance_logging: true
security:
mandatory_encryption: true
audit_logging: true
policy_enforcement: true
Testing Custom Builds
Virtual Testing
Test builds in virtual environments:
# Test with QEMU
qemu-system-arm -M raspi3 -kernel kernel.img -dtb bcm2710-rpi-3-b.dtb
# Test with Docker
docker run --privileged -v $(pwd)/output:/images haxinator-test
Hardware Testing
Test on actual hardware:
- Flash Image: Flash custom image to SD card
- Boot Test: Verify successful boot
- Feature Test: Test all custom features
- Performance Test: Verify performance meets requirements
Distribution
Image Optimization
Optimize images for distribution:
# Compress image
gzip output/haxinator-custom.img
# Create checksums
sha256sum output/haxinator-custom.img.gz > checksums.txt
# Create torrent (optional)
mktorrent output/haxinator-custom.img.gz
Documentation
Document your custom build:
- Feature List: Document included features
- Installation Guide: Custom installation instructions
- Configuration Guide: Pre-configured settings
- Changelog: Changes from base image
Troubleshooting
Build Issues
Common build problems and solutions:
Dependency Errors
# Update package lists
sudo apt update
# Install missing dependencies
sudo apt install --fix-missing
Space Issues
# Check available space
df -h
# Clean build cache
./build.sh --clean
Permission Issues
# Fix permissions
sudo chown -R $USER:$USER build/
chmod +x build.sh
Runtime Issues
Debug custom build issues:
- Boot Problems: Check kernel and device tree
- Service Failures: Check systemd logs
- Network Issues: Verify network configuration
- Tool Problems: Check tool installation and permissions
Contributing Custom Builds
Sharing Builds
Share your custom builds with the community:
- Document Build: Create comprehensive documentation
- Test Thoroughly: Ensure build works on multiple devices
- Submit PR: Submit pull request with build configuration
- Community Review: Participate in community review process
Build Templates
Create reusable build templates:
# templates/security-researcher.yml
name: "Security Researcher Build"
description: "Optimized for security research and testing"
features:
- all_tunneling_methods
- security_tools
- network_analysis
- custom_scripts
Next Steps: Learn how to contribute to the Haxinator 2000 project.