Securing SSH Access for Multiple Developers

SSH is the backbone of server access. Doing it right saves a lot of headaches.

Create individual keys

Each developer generates an SSH key:

ssh-keygen -t ed25519 -C "dev1@example.com"

ssh-keygen -t ed25519 -C "[email protected]"

Add keys to the server

mkdir -p ~/.ssh
echo "ssh-ed25519 AAAA... user@host" >> ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys
chmod 700 ~/.ssh

mkdir -p ~/.ssh
echo "ssh-ed25519 AAAA... user@host" >> ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys
chmod 700 ~/.ssh

Disable password login

PasswordAuthentication no
PermitRootLogin no

PasswordAuthentication no
PermitRootLogin no

Then restart SSH

sudo systemctl restart sshd

sudo systemctl restart sshd

Optional: restrict users by IP

Add AllowUsers [email protected].* to limit access.

This keeps your servers secure while letting multiple developers work without shared credentials.