https://bugs.kde.org/show_bug.cgi?id=420902
--- Comment #3 from Florian Bruhin <[email protected]> --- Agreed that there isn't a proper, clean fix for this. Still, remembering insecure hostnames and always treating them as insecure seems like an acceptable workaround: While still showing "insecure" when the problem is fixed server-side is unfortunate, it's still much better than showing "secure" when the connection isn't. FWIW I added a comment here: https://bugreports.qt.io/browse/QTBUG-80860?focusedCommentId=510104&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-510104 -- You are receiving this mail because: You are watching all bug changes.
