New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
put content of pub file in the /root/.ssh/authorized_keys file (if you want to login to root) or /home/user_X/.ssh/authorized_keys file (if you want to login to user_X)
scp mahkey [email protected]:/root/.ssh/authorized_keys
THANK YOU SO MUCH.
Any good projects that generate and manage a small fleet of keys?
putty & puttygen
You can use the same key on each server. Just make sure it's secure (either Ed25519 or 4096-bit RSA, and password protected). The server only has the public key on it, which is safe to share. It's the private key (on your client side) that you need to keep secure.
I use one key per client device (one for my desktop PC, one for my tablet, one for my phone, etc, and one for Ansible). Occasionally "important" servers also use a separate key per device.
Telnet > ssh
Less overhead = faster and more performant access to your terminal.
ssh is bloat
Telnet isn't encrypted. More performant command line? Wut? If you're needing the performance difference between telnet and ssh for typing commands, you need a better server.
Well, this is not something I expected to read on LET.
Not quite - you missed quite a few potential pitfalls. If the user is user_X:
On my LXC machine I couldn't connect using my public key before I had also changed sshd_config to "PubkeyAuthentication yes". I read somewhere that you shouldn't have to change sshd_config and pub key is accepted by default, but on that LXC install it didn't work before I also updated sshd_config to accept public keys.
relax, it was a quick, high-level instruction for an inteligent human being (able to create folder and file if it does not exist yet), not a full script for a dumb bot
and OP succeeded and solved his problem and moved on
asap, not 2 days later
btw. ssh server daemon is intelligent enough to articulate if he does not like permission/ownership of key files (especially private one), no need to overengineering everything
You should turn
user_X
into a variable you set at the top if it's intended for newbie copy and paste. So many people just got errors about "user_X" path not existing.https://www.digitalocean.com/community/tutorials/how-to-create-ssh-keys-with-putty-to-connect-to-a-vps