I think a gsk trace would be a helpful solution.
On Fri, Jan 31, 2020 at 1:55 PM Steve David <[email protected]> wrote: > Hi All, > We are planning to upgrade CD V4.8 to V5.2, we lost the key to open the key > database which used for secure+ encryption. We have used GSKKYMAN utility > to generate the certificate and signed by third party CA. > > SECURE.SSL.PATH.PREFIX =/usr/lpp/connectd/conn.kdb, > > We have couple of certificates mentioned in above path, out of which one is > expiring in Mar 2020 and other one in Nov 2020, Is there a way to find > which certificate is in use for SSL > Encryption? > > Thanks > Steve > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Politics: Poli (many) - tics (blood sucking parasites) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
