Re: process to generate a new RSA Connection key.

[Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>]

I have been struggling with this for too long, so I'll just ask some
obvious questions.
We SSH to many different customers/vendors, but use the SAME profile  (i.e.
same /home/USERPRF/.ssh path/key)
Is this normal/ proper/ crazy as heck ?

I see that SSH keys "don't expire", but a vendor requires we have a new key
every 2 years.  is there a process to
only generate a new public for them, leaving the other public key alone
that all the other cust/vend use?

On Mon, Dec 4, 2023 at 11:34 AM Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
wrote:

> The process I have to create a new RSA connection key (current key is
> about to expire)
> is to  first save "id_rsa" and "id_rsa.pub"  with a yyyy extension.
> then    "ssh-keygen –t rsa –N “”  "
> then rename the new id_rsa, id_rsa.pub files  with new expire year (2
> years)
> then rename the first files back.
> the next process is to send the new id_rsa.pub file to our bank for
> "testing and approval".
> when approved, we can set the new files to "active" (drop the year
> extension).
> and send the new public key to the other vendors we connect to via ssh.
>
> we only use one ibm i user profile for all of our ssh communications.
>
> I don't think this is how it is supposed to work, but I can't find good
> instructions on "renewing" a RSA connection key.