For my znc IRC bouncer I use a cacert class 3 certificate. The cacert class 3 is accepted as a valid certificate in both KDE's SSL settings and openssl's ca's list. Connecting using https with either firefox, wget and konqueror works flawlessly, but when using konversation it complains that the certificate is not signed by a trusted CA despite both the class 3 and the root certificates provided in the chain are marked as trusted. Since this is only happening with konversation I think the bug is in its SSL handling code. Reproducible: Always Steps to Reproduce: 1. Add the cacert class 3 CA as a trusted CA 2. connect to irc.xiscosoft.es:7000 using SSL 3. konversation complains the certificate isn't trusted 4. Displaying the certificate chain shows the issue is that the certificate isn't signed by a trusted CA yet both of the other certificates in the certificate chain are shown as trusted. Actual Results: SSL connection error, the user is required to accept a bogus warning Expected Results: No SSL error as happens with the other clients
As a comment any KDE developer is welcome to test connecting to that server to test the issue by themselves, if a user is needed I can create one too.
For the record the issue still remains on Konversation 1.5.1
Thanks for the report klondike. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!