Unified PEM certificate requires duplicate x509 PEM listing under Private Key

[knakamura8]

Some IRC servers support CertFP using a pem file. I have checked directions across several popular servers, and many prefer when users make a pem file in x509 cert format containing a public/private pairing.

In KVIrc, when checking the Use SSL certificate (PEM format only) box, and pointing to the certificate location, clicking Apply, OK, and then attempting to connect with the cert, servers do not issue fingerprints. I was puzzled briefly, then checked the logs and realized that the private key was not being used within the pem file. Checking the Use SSL private key box and pointing the private key location to the same exact pem file fixed this issue.

I feel as though this is unclear to users, and that if a pem file is checked and private key is unchecked, KVIrc should automatically attempt to utilize a private key from within the pem file.