Summary: | Invalid server certificates cannot get accepted "forever" | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Daniel Hahler <kde-bugzilla> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | adawit, finex, jammer, lynoure |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Daniel Hahler
2006-08-21 22:03:30 UTC
Please mark it as DUP of Bug 143898, which seems to be the same issue. btw: the certificate from the address above has likely changed since I initially reported this bug. *** Bug 143898 has been marked as a duplicate of this bug. *** Bug confirmed on both 3.5.9 and 4 (trunk r806921). (In reply to comment #0) > But, after I reboot (or maybe just re-login - have not tried it) the same > warning appears again. > > It does not appear again just after "killall konqueror". The problem reappears as soon as you reload the page. Konqueror changes the KSSL policy back to one hour, not permanent. See my comments: https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/93081/comments/15 Duplicate of 207050? I cannot duplicate this at all in KDE v4.6 and up. Does anyone still have this issue using KDE v4.6 or better yet KDE v4.7 beta 1 ? When I choose forever my certificate is stored with a date 1000 years from current year (3011). I can confirm that this issue is present in my version of Konqueror "Version 4.6.5 (4.6.5) Using KDE Development Platform 4.6.5 (4.6.5)" This is however a recent regression as Konq from KDE v4.4 did not exhibit this behaviour. Specifically I am connecting to https://localhost/ which uses an unsigned certificate. "Would you like to accept the certificate forever without being prompted ?" Forever Current Session only I click "Forever" and am again presented with the same dialogue for all other pages on this host. *** This bug has been marked as a duplicate of bug 233628 *** |