SSH Management
Manage SSH connections with Kerminal's powerful profile system.
Creating Profiles
- Open SSH Profiles panel (
Ctrl+Shift+S) - Click New Profile
- Fill in connection details:
| Field | Description |
|---|---|
| Name | Profile display name |
| Host | Hostname or IP |
| Port | SSH port (default: 22) |
| Username | SSH username |
| Auth | Password or SSH Key |
Organizing Profiles
Groups
- Click New Group
- Drag profiles into groups
- Collapse/expand as needed
Colors
- Edit profile → Terminal tab
- Select Tab Color
- Color shows in sidebar and tabs
Authentication
Password
Enter password when creating profile. Encrypted with AES-256-GCM.
TIP
Consider SSH keys for better security.
SSH Keys
- Select SSH Key as auth method
- Choose existing key or click Manage SSH Keys
Key Manager
- Generate: RSA, Ed25519, ECDSA
- Import: From file or clipboard
- Export: Public key for servers
Network Options
Proxy
- Edit profile → Network tab
- Enable Use Proxy
- Select type: HTTP, SOCKS4, SOCKS5
- Enter proxy details
Jump Hosts
Connect through bastion servers:
Local → Bastion → Target- Create bastion profile first
- In target profile → Network tab
- Enable Use Jump Host
- Select bastion profile
Chained jumps: Add multiple jump hosts in order.
Port Forwarding
Local Forward
Access remote services locally:
localhost:8080 → remote:80Use case: Access web UIs, databases
Remote Forward
Expose local services remotely:
remote:8080 → localhost:3000Use case: Share dev server, webhook testing
Dynamic (SOCKS)
Create SOCKS proxy through SSH:
Local port 1080 → SOCKS5 proxyUse case: Browse through remote network
Enable Auto-start to establish tunnels on connect.
Import & Export
From ~/.ssh/config
- Look for From .ssh/config section
- Click Import button
- Select hosts to import
Backup & Restore
- Click Backup & Restore in top bar
- Export: Save profiles as JSON (password protected optional)
- Import: Restore from backup file
Testing Connections
Before saving:
- Fill in all details
- Click Test Connection
- View results: success, auth error, or network error
Best Practices
Security
- Use SSH keys over passwords
- Protect keys with passphrases
- Rotate keys periodically
Organization
- Group by environment (prod, staging, dev)
- Use descriptive names
- Color-code for quick identification
