SSH Access and Authentication
This document outlines the SSH access setup for the Hadox infrastructure, covering the VPS and Hostinger shared hosting environments.
1. VPS Access (srv566867)
Provider
- Host: Hostinger VPS
- OS: Ubuntu 22.04.5 LTS
SSH Configuration
- Default SSH port:
22 - Primary user:
root(restricted usage recommended) - Limited user:
drone(used for CI deployments)
Key-based Authentication
- SSH keys are used exclusively; password login is disabled.
- Each key is generated per environment (local, Drone CI, etc.)
Known SSH Keys
| Environment | Key name | User | Notes |
|---|---|---|---|
| Local Dev | hostinger-deploy |
ekaropolus |
For pushing from local to Hostinger |
| CI/CD | drone-hostinger |
drone |
Used by Drone CI to pull/push code |
| Gitea | git@hadox.org |
system | System-wide access for Gitea Git |
2. Hostinger Shared Hosting
SSH Settings
- Custom port:
65002 - SSH user:
u594326895 - Access: Git-based deployment only
- Restrictions:
- No root privileges
- No Docker support
- Git pull operations permitted from verified remotes
3. Key Management
All SSH keys should be:
- Generated with
ssh-keygen -t ed25519 - Stored securely (
~/.ssh/) - Added to appropriate services (e.g., Gitea, GitHub, Hostinger)
- Documented in this file upon creation
Common SSH Commands
# Test connection
ssh -p 22 root@<vps-ip>
# Add new key to agent
ssh-add ~/.ssh/hostinger-deploy
# Test Git operations
git -c core.sshCommand="ssh -i ~/.ssh/hostinger-deploy -p 65002" pull
Security Recommendations
- Disable root login for production (future hardening)
- Rotate keys periodically
- Avoid password-based authentication