SSH Operations
Secure shells. Encrypted tunnels. Key-based access.
CLASSIFIED SCENARIO
Your handler at LANGLEY has established a covert relay through Tor. Standard communications are compromised. You must establish a secure SSH tunnel using key-based authentication to transmit extracted UMBRA intercepts. Password authentication is disabled - only your cryptographic keys will grant access.
Why SSH Mastery Matters
SSH (Secure Shell) is the primary tool for remote operations. Every serious operator must understand:
- Encrypted communications - All traffic is cryptographically secured
- Key-based authentication - No passwords to intercept or brute-force
- Secure file transfer - Move intel without exposure
- Port forwarding - Tunnel through firewalls and proxies
- Remote command execution - Operate systems from anywhere
SSH Attack Surface
- Password auth enabled - Brute force opportunity
- Weak key algorithms - DSA, 1024-bit RSA vulnerable
- SSH agent forwarding - Key theft on compromised jump hosts
- Known hosts bypass - Man-in-the-middle potential
- Private keys on disk - Recovery from compromised systems
Core SSH Commands
ssh
Connect to remote systems. The foundation of remote operations.
ssh-keygen
Generate cryptographic key pairs. Ed25519 recommended for modern ops.
ssh-copy-id
Deploy public keys to remote systems for passwordless access.
scp
Secure copy - transfer files over SSH. Fast, encrypted, reliable.
Command Deep Dive
ssh-keygen - Generate Keys
$ ssh-keygen -t ed25519 -C "operator@blacksite"
Generating public/private ed25519 key pair.
Enter file in which to save the key (/home/operator/.ssh/id_ed25519):
Enter passphrase (empty for no passphrase): ********
Enter same passphrase again: ********
Your identification has been saved in /home/operator/.ssh/id_ed25519
Your public key has been saved in /home/operator/.ssh/id_ed25519.pub
[OPSEC] Ed25519 is the most secure, fast algorithm
[OPSEC] ALWAYS use a passphrase - protects if key is compromised
ssh-copy-id - Deploy Keys
$ ssh-copy-id handler@relay.onion.net
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/home/operator/.ssh/id_ed25519.pub"
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed
handler@relay.onion.net's password:
Number of key(s) added: 1
[SUCCESS] Public key installed in ~/.ssh/authorized_keys
[INFO] Future logins will use key, not password
ssh - Connect Securely
$ ssh handler@relay.onion.net
Enter passphrase for key '/home/operator/.ssh/id_ed25519':
Welcome to LANGLEY RELAY ALPHA
[CONNECTED] Encrypted tunnel established
[SECURE] 256-bit AES-GCM encryption active
scp - Secure File Transfer
$ scp -r /intel/UMBRA_intercepts/ handler@relay.onion.net:/drop/
UMBRA_001.enc 100% 45KB 1.2MB/s 00:00
UMBRA_002.enc 100% 32KB 980KB/s 00:00
UMBRA_manifest.gpg 100% 2.1KB 500KB/s 00:00
[EXFIL] 3 files transferred securely
[OPSEC] Traffic encrypted end-to-end
Quick Reference
| Command | Purpose | Key Flags |
|---|---|---|
ssh user@host | Connect to remote | -i (key), -p (port) |
ssh-keygen -t ed25519 | Generate key pair | -C (comment), -f (file) |
ssh-copy-id user@host | Install public key | -i (specific key) |
scp src user@host:dst | Copy files | -r (recursive), -P (port) |
ssh -L port:host:port | Local port forward | Tunnel to internal hosts |
ssh -D port | SOCKS proxy | Dynamic port forwarding |
SSH Operations Workflow
# === COVERT CHANNEL SETUP ===
$ ssh-keygen -t ed25519 -C "op" # 1. Generate secure keys
$ ssh-copy-id handler@relay # 2. Deploy to handler
$ ssh handler@relay # 3. Establish tunnel
$ scp intel.tar.gz handler@relay: # 4. Exfiltrate data
# Pro tip: Add to ~/.ssh/config for quick access:
Host handler
HostName relay.onion.net
User handler
IdentityFile ~/.ssh/id_ed25519
Ready to Establish Contact?
Test your SSH knowledge, then establish the covert tunnel.