Server Authenticity check dialog pops up on startup, even though the certificate is saved forever. Reproducible: Always Steps to Reproduce: 1. Connect to an IRC server that supports SSL, but without a signed certificate from a trusted authority. 2. Save the certificate 'forever' in the following dialogue. 3. Restart Konversation, and connect to the same server.
I can confirm the same behavior in 1.5. To reproduce: add freenode and use the server name chat.au.freenode.net. Because the wildcard certificate doesn't match you'll get the SSL error, click to accept an exception and click to save it forever. Upon any reconnect you will get the same error.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Hello Andrew. Thanks for checking the bug report. I filed this a long time back and I don't use KDE these days. It'll be a lot of work to setup everything to test this one bug. Please delete the report (I don't see an option to do so). Thanks.
Thanks for the update!
(In reply to Andrew Crouthamel from comment #2) > Dear Bug Submitter, > > This bug has been stagnant for a long time. Could you help us out and > re-test if the bug is valid in the latest version? I am setting the status > to NEEDSINFO pending your response, please change the Status back to > REPORTED when you respond. > > Thank you for helping us make KDE software even better for everyone! freenode uses proper certificates now, so I don't have a means to test the problem as it existed before. So, the problem may or may not exist, but I don't have an easily accessible means of testing it myself--I'd have to setup my own XMPP server and use a self-signed cert. I'm a bit busy to take that on right now.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
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!