Re: SOLVED, Re: Secured Telnet from one Midrange box to another

Yeah, I've went to each lpar and did the "Populate with CA certificates".
This was required to get many of the IBM i SQL services which consume data
from websites to work.
I kind of though James already went through that battle. Perhaps pub400
uses a chain not commonly found in that pond. Or I may be thinking of
someone besides James.

On Thu, Apr 6, 2023 at 5:45 AM Marc Rauzier <marc.rauzier@xxxxxxxxx> wrote:

Le 06/04/2023 à 03:14, Patrik Schindler a écrit :

Hmm. Doesn't IBM provide a system-wide installed collection of common

root-CA certificates, like modern browsers have integrated nowadays?

I think it was the case until V7R2.

When V7R3 was released, IBM changed the behavior. Look at the Memo to
users for V7R3 and DCM:

https://www.ibm.com/docs/en/i/7.3?topic=options-digital-certificate-manager-5770-ss1-option-34

--- quote ---

When creating a certificate store using Digital Certificate Manager in
IBM® i 7.3, the default list of Root Certificate Authority (CA)
certificates no longer get automatically added to the certificate store.
To add CA Root certificates to a newly created certificate store, select
“Manage Certificate Store” from the left side pane and then select the
option to “Populate with CA certificates”.

The “Populate with CA certificates” panel allows you to select the CA
Root and Intermediate certificates you trust to be added to the
certificate store by placing a checkbox next to the desired certificates
and then clicking on the “Continue” button. The certificates which are
listed include secure versions using Secure Hash Algorithm (SHA-2)
signature algorithms with an RSA key size of 2048 bits or greater or an
ECDSA key size of 256 bit or greater.

--- quote ---

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.