Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Rabisu - Hosting Solutions
Shells Virtual Desktop
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.

After generating a new SSH key, the old one is still active?

vahevahe Member
edited April 2012 in General

I generated a ssh key on my local machine, and uploaded the id_rsa.pub and renamed it to authorized_keys. I could connect to the server no problem. Then I removed the id_rsa from my local machine and generated a new key, again on the same machine. Now, without uploading the new id_rsa.pub public key, I can still ssh to the server.
Why does this happen? Don't the key pairs have to match? How can I disable the old key?

Comments

  • Delete the old key from the server and restart SSH.

    Thanked by 1vahe
  • vahevahe Member

    Thanks, this works. But why am I able to connect if I have the old key on the server, but not on my local machine?

    Thanked by 1dnom
  • NickMNickM Member

    If you're using Linux, the old key may have been cached in memory by ssh-agent.

    Thanked by 1djvdorp
Sign In or Register to comment.