rry more about your character than your reputation. Character is what
> you
> > are, reputation merely what others think you are.” - - - John Wooden
> >
> > -Original Message-
> > From: IBM Mainframe Discussion List On
> Behalf Of
&
IBM Mainframe Discussion List On Behalf Of
> Allan Staller
> Sent: Tuesday, May 23, 2023 7:45 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Replacing SSH Keys - best practices?
>
> Classification: Confidential
>
> It is not necessary to remove the "old keypair".
When you think about renewal guidelines for SSH keypairs, the relevant
question is: What do you want to protect yourself (or your org) against?
If you account for the possibility that the private key itself gets into
wrong hands unknowingly, it boils down to the computational effort to
make the
at works.
Theoretically, at some point this could become a performance bottleneck. In
practical terms it seems to be a non-issue.
My USD $0.02 worth.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Lionel B. Dyck
Sent: Tuesday, May 23, 2023 7:39 AM
To: IBM-MAIN@LIST
ssue.
My USD $0.02 worth.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Lionel B. Dyck
Sent: Tuesday, May 23, 2023 7:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Replacing SSH Keys - best practices?
[CAUTION: This Email is from outside the Organization. Unless y
0.02 worth.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Lionel B. Dyck
Sent: Tuesday, May 23, 2023 7:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Replacing SSH Keys - best practices?
[CAUTION: This Email is from outside the Organization. Unless you trust the
sen
For those into security (and shouldn't we all be) a question on ssh keys:
How often should a user change their ssh keys for z/OS (OMVS)? on their
workstation?
When changing on the workstation, that probably happens every few years as
the workstation is replaced, the user then needs to update
