Share SSH Access the Right Way: Keys, Not Passwords

Why passwords are the wrong tool for SSH

Server passwords end up in chats, tickets, and inboxes—and linger for years. SSH keys are safer: you share only the public key, keep the private key local, and can revoke access without changing a master password.

Step-by-step (safe and fast)

1. Generate a keypair on your machine (don’t share the private key). Use a strong passphrase for the key—learn how to make one you’ll remember: Create Strong Passphrases.
2. Share only your public key (the .pub file) with the server admin using a one-time, expiring link and a separate access code. Basics: The Safe Way to Share Passwords in 2025 (No Email).
3. Admin installs it into ~/.ssh/authorized_keys, ideally on a non-root user with least privilege.
4. Test access, then tighten: disable password auth, restrict by command or IP if needed.

Operational hygiene

• Per-person keys—never reuse a single key for a whole team.
• Rotate on handoff and when people leave. Offboarding tips: 90-Minute Sweep and Leaked Passwords Playbook.
• Store secrets in a password manager (notes for key passphrases, not the key itself).

Useful external references

• OpenSSH Project 🔗
• GitHub: Generate & add an SSH key 🔗

Related reading

Developer handoffs: Share API Keys and .env Files (Safely)

Zero-knowledge delivery basics: The Beginner’s Guide to Zero-Knowledge Sharing

Phishing-safe link habits: Verify Links Like a Pro

Bottom line

Keys beat passwords for SSH. Share the public key via a one-time link, lock down roles, and rotate when people change.

Secure One-Time Messages - Send confidential messages that self-destruct after being read once. Your privacy is our priority. →.